namespace_list

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

Annotations already declare readOnlyHint=true, and the description reinforces this with a [READ] tag. It adds value by disclosing the returned fields (name, phase, age), which matters since there is no output schema, but says nothing about scope across clusters, pagination, or filtering.

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?

Front-loaded with the read tag and purpose, and the Args block is minimal with zero filler. Appropriately sized for a one-parameter list tool.

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?

Since there is no output schema, listing the return fields (name, phase, age) is the right compensating detail, and the read-only nature is clear. Minor gaps remain around cluster scope and result size, but for a simple list operation this is largely complete.

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 0%, so the description carries the full burden for the single 'target' parameter, and it does explain it: 'k8s target name from config; omit to use the default.' That clarifies meaning and default behavior absent from the schema.

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+resource ('List namespaces') and even enumerates the returned fields (name, phase, age), so the agent knows exactly what it produces. It doesn't explicitly distinguish itself from create_namespace/delete_namespace siblings, but the 'List' verb and [READ] tag make the intent obvious.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The only guidance is embedded in the 'target' arg note (omit to use the default), which is parameter-level rather than usage-level.

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