list_deployments

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

With no annotations, the description must fully disclose behavioral traits, but it only states 'List recent deployments' without explaining what 'recent' means, whether the output is ordered or paginated, or what the optional namespace parameter does. This leaves the agent unaware of the full operational semantics.

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 a single, short sentence with no filler words, which is concise. However, it is too sparse and omits important details like the namespace filter and the meaning of 'recent', making it under-specified rather than effectively concise.

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 tool is relatively simple with one optional parameter and no output schema or annotations, but the description is incomplete. It fails to explain the namespace parameter, the notion of 'recent', or return characteristics, leaving the agent unable to make a fully informed decision about invocation.

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?

The input schema has one optional parameter 'namespace' with a type of string, but the description offers no explanation of this parameter. Since schema description coverage is 0%, the description should have compensated by mentioning that the namespace filter is supported, but it does not, providing zero added meaning.

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 uses the specific verb 'List' and resource 'deployments' with scope 'across the cluster', making the core purpose clear. It is distinguishable from siblings like get_deployment (single deployment) and get_job_deployments (deployments for a specific job), though the term 'recent' is vague and doesn't fully specify whether it includes all or a filtered subset.

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 guidance is provided on when to use this tool versus alternatives such as list_jobs or get_job_deployments. There is no mention of context, prerequisites, or exclusions, leaving the agent without direction for tool selection.

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