getDoraMetrics

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

With no annotations, the description must disclose behavioral traits on its own. It only mentions 'configured service,' implying a prerequisite, but doesn't explain what configuration entails, auth requirements, rate limits, output format, or error behavior. This is insufficient for a tool with no annotation support.

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?

Two concise, front-loaded sentences with no filler. Every word contributes to understanding the tool's core purpose and a parameter detail.

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 no annotations, no output schema, and only two parameters, the description is too sparse. It fails to explain how metrics are calculated, what 'configured' means, the default 'since' if omitted, or what the response looks like. The tool is moderately complex, and this description leaves major gaps.

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 coverage is 0%, so the description must compensate. It does add meaning by explaining the 'since' parameter format ('values like '30d'') and hinting that 'service' refers to a configured service. However, it doesn't document any default behavior, acceptable formats for 'service', or further parameter details.

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 tool's function: getting DORA metrics with specific metric names. It uses a specific verb ('Get') and resource ('DORA metrics'), and the metrics list (deployment frequency, lead time, etc.) distinguishes it from sibling tools like getRecentDeployments or getRecentIncidents.

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 usage context is implied: you use this when you need DORA metrics for a service. However, there is no explicit guidance on when to prefer this tool over siblings or when not to use it, nor any mention of alternatives.

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