Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true, so the description must carry the rest — and it does, disclosing the list metadata response shape (total, returned, truncated, scope) that lets the agent detect truncation. It stops short of auth/permission or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with the returned fields before the listing constraint. Every clause carries information, though the field enumeration is packed tightly enough to border on a run-on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by naming the returned fields and the list metadata (total/returned/truncated/scope). Coverage of the read behavior is complete for an agent to invoke it correctly, missing only edge details like error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all four parameters are already documented, including the namespace/all_namespaces rule and the cluster_id discovery hint. The description largely restates this; baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch) and resource (Ingress summary rows), then enumerates exactly what each row contains: name, namespace, hosts/paths, backends, LB addresses, TLS hosts/secrets, age. This resource is unique among siblings (get_services, get_pods, get_configmaps), so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a scope precondition for listing ('needs namespace or all_namespaces=true') but offers no explicit when-to-use vs alternatives guidance — nothing routes the agent between get_ingresses, describe_resource, or trace_request_path. Usage is only implied by the resource name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.