list_deployments

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

No annotations are provided, so the description carries full burden. It states the tool lists deployments, implying a read-only operation, but fails to disclose behavioral details such as permissions required, pagination, error handling, or what happens on invalid inputs.

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?

The description is concise, using two lines for the main purpose and a bullet list for parameters. However, the param details could be integrated into the main sentence for better front-loading.

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?

The description covers the tool's action and parameter usage but lacks context on output behavior (though an output schema exists) and potential errors. It is minimally adequate for a simple tool.

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?

With 0% schema description coverage, the description adds value by explaining 'cluster_id' as 'Rancher-assigned cluster identifier' and 'namespace' as 'Optional namespace to filter deployments.' This goes beyond the schema's bare titles.

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?

The description clearly states 'List Deployments in a cluster, optionally scoped to a namespace.' This provides a specific verb ('list') and resource ('deployments') with scope ('cluster', 'namespace'), effectively distinguishing it from sibling tools like 'scale_deployment' or 'list_clusters'.

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 no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it or provide context for choosing among siblings like 'list_pods' or 'list_namespaces'.

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