list_dora_deployments

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, pagination behavior, default ordering, or rate limits. The parameters 'page_size' and 'page_cursor' hint at pagination but are not explained. The description carries the full burden and fails to convey safety or performance aspects.

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 sentence, which is concise, but it is too brief to be informative given the complexity of the tool. It earns its place by stating purpose, but more detail is needed. The score reflects that while not wordy, it is under-specified.

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?

With 6 parameters, no output schema, and no annotation support, the description should provide substantial context. It only hints at the metric domain (DORA) but does not explain what a deployment is, how filters work, or what the response contains. This is insufficient for a listing tool of moderate complexity.

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%, meaning no parameter descriptions exist in the schema. The description does not explain any of the 6 parameters (e.g., filters, pagination). It merely restates the tool's purpose without linking to parameter usage, leaving the agent with no semantic understanding of input fields.

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 the action 'List' and the specific resource 'DORA metric deployments', and mentions the purpose 'for tracking deployment frequency and lead time'. This distinguishes it from other list tools among siblings, as none explicitly target DORA 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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, constraints, or comparison with other listing tools. The description lacks any context for usage decisions.

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