list-fleet-tracers

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

Description does not contradict annotations (none provided). Mentions filtering, implying read-only behavior, but no details on pagination, limits, or side effects. With no annotations, description carries full burden but only provides basic info.

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?

Single concise sentence, front-loaded with key information. No extraneous text. Appropriate length for a simple list tool.

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?

No output schema, so agent lacks return format information. Description is brief but covers basic purpose and parameters. For a simple list operation with full schema coverage, this is minimally complete.

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 100%, so baseline is 3. Description only says 'with filtering', adding no additional meaning beyond schema. No details on filter format or parameter relationships.

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?

Clear verb+resource: 'List fleet tracers' and provides helpful clarification 'telemetry-derived service names'. However, does not differentiate from sibling tools like list-services or list-fleet-agents, which could cause confusion.

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 explicit guidance on when to use vs alternatives. Implies usage for listing tracers with filtering, but lacks context on when not to use or mention of sibling tools. This is adequate but minimal.

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