[Automated] Draft docs (agentgateway): filters: better error handling

content/docs/standalone/main/documentation/configuration/resiliency/mirroring.md

@@ -18,6 +18,7 @@ Attaches to: {{< badge content="Route" path="/documentation/configuration/routes
 
 Request {{< gloss "Mirroring" >}}mirroring{{< /gloss >}} allows sending a copy of each request to an alternative backend.
 These requests will not be retried if they fail.
+Set `percentage` to a value from `0.0` to `1.0`. For example, `0.5` mirrors half of the requests. Agentgateway rejects a configuration with a value outside that range, such as `percentage: 50`.
 
 {{< tabs >}}
 {{< tab name="Simplified (MCP)" >}}

content/docs/standalone/main/documentation/configuration/traffic-management/direct-response.md

@@ -58,6 +58,8 @@ routes:
 {{< /tab >}}
 {{< /tabs >}}
 
+Set either `body` or `bodyExpression`, not both. Agentgateway rejects a configuration with a direct response policy that sets both fields.
+
 {{< doc-test paths="direct-response" >}}
 cat <<'EOF' > config.yaml
 # yaml-language-server: $schema=https://agentgateway.dev/schema/config

content/docs/standalone/main/documentation/configuration/traffic-management/manipulation.md

@@ -21,6 +21,7 @@ There are a few different policies that offer manipulation of HTTP requests and
 The `requestHeaderModifier` and `responseHeaderModifier` modify request and response headers respectively.
 These allow you to `add`, `set`, or `remove` headers.
 `add` and `set` differ in the case the header already exists; `set` will replace it while `add` will append.
+Agentgateway rejects a configuration with a header modifier that contains an invalid HTTP header name or value.
 
 {{< tabs >}}
 {{< tab name="Simplified (MCP)" >}}

content/docs/standalone/main/documentation/configuration/traffic-management/redirects.md

@@ -18,6 +18,8 @@ Attaches to: {{< badge content="Route" path="/documentation/configuration/routes
 
 Request {{< gloss "Redirect" >}}redirects{{< /gloss >}} allow returning a direct response redirecting users to another location.
 
+Start the `path.full` and `path.prefix` values with `/`. If you use `path.prefix` on a route that does not delegate to a route group, every match on the route must use `pathPrefix`. Agentgateway rejects a configuration that does not follow these rules.
+
 For example, the following configuration will return a `307 Temporary Redirect` response with the header `location: https://example.com/new-path`:
 
 {{< tabs >}}

content/docs/standalone/main/documentation/configuration/traffic-management/rewrites.md

@@ -18,6 +18,8 @@ Attaches to: {{< badge content="Route" path="/documentation/configuration/routes
 
 Modify URLs of incoming requests with {{< gloss "Rewrite" >}}rewrite{{< /gloss >}} policies.
 
+Start the `path.full` and `path.prefix` values with `/`. If you use `path.prefix` on a route that does not delegate to a route group, every match on the route must use `pathPrefix`. Agentgateway rejects a configuration that does not follow these rules.
+
 For example, the following configuration modifies the request hostname to `example.com` and the request path to `/new-path`.
 
 {{< tabs >}}