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. It only states that it lists deployments, but fails to mention aspects like pagination, order, filtering, or whether it returns all deployments across all applications. The minimal description does not meet the burden of transparency.

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, clear sentence. It is concise and front-loaded with the action. While it could be expanded slightly to add context, it currently contains no wasted 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?

The tool has no output schema and no annotations. The description is extremely minimal for a list operation; it should ideally convey what the list contains, if there are any defaults (e.g., sorted by date), and whether the list is paginated. This lack of detail makes it incomplete for an AI to infer expected behavior.

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 tool has zero parameters, and the schema description coverage is 100%. The description does not need to add parameter information since there are none. However, it could still mention the absence of filters for completeness, so the score is slightly below perfect.

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 'List all deployments' clearly states the action (list) and resource (deployments). It is a specific verb+resource combination. However, the scope of 'all' is ambiguous—whether it means all deployments globally or within a context—which slightly reduces clarity, though it is still distinguishable from sibling tools like 'get_application_deployments'.

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 usage guidance is provided. There is no indication of when to use this tool versus alternatives such as 'get_application_deployments' or 'get_deployment'. The description does not mention any context or prerequisites, leaving the AI with no basis for decision.

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