ingress_list

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

Prefix '[READ]' signals read-only. Lists output fields but does not mention pagination, rate limits, or required permissions. With no annotations, description carries burden but provides only minimal behavioral detail.

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?

Extremely concise: three lines total. Purpose stated first, followed by parameter descriptions. No unnecessary words.

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?

Sufficient for a simple listing tool with two parameters. No output schema, but return fields are listed. Could improve by noting alphabetical order or sorting.

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?

Both parameters explained: 'namespace' can be omitted for all namespaces, 'target' from config. Adds meaning beyond schema (strings) even though schema coverage is listed as 0%.

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?

Clear verb+resource: 'List ingresses' with output fields (name, namespace, class, hosts, age). Distinguishes from sibling 'ingress_get' which retrieves a single ingress.

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?

Describes parameters but lacks explicit guidance on when to use vs alternatives (e.g., ingress_get for details). No context on typical use cases.

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