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 'Get the list' which implies a read-only operation, but doesn't disclose behavioral traits like pagination behavior (implied by limit/offset in schema but not described), authentication needs, rate limits, or what happens if no deployments exist. It's minimal and lacks context.

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 very concise with a single sentence 'Get the list of deployments', which is front-loaded and wastes no words. However, it's arguably too brief given the tool's complexity, but within the conciseness dimension, it scores well for efficiency.

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?

Given the complexity (1 nested parameter with 5 sub-properties, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's behavior, parameter usage, or return values, leaving significant gaps for an AI agent to understand how to invoke it correctly in context with sibling tools.

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 description coverage is 0%, so the description must compensate for undocumented parameters. The description provides no information about parameters, not even mentioning that filtering or pagination is possible. With 1 parameter (a nested object with 5 sub-properties) and no param info in the description, it fails to add meaning beyond 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?

The description 'Get the list of deployments' states a clear verb ('Get') and resource ('deployments'), but it's vague about scope and doesn't distinguish from sibling tools like 'get-deployment' or 'list-apps'. It lacks specificity about what kind of deployments or what context.

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 on when to use this tool versus alternatives. It doesn't mention when to use 'list-deployments' instead of 'get-deployment' (which likely retrieves a single deployment) or other list tools like 'list-apps' or 'list-services'. No context or exclusions are provided.

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