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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true and destructiveHint as false, which the agent can rely on. The description adds valuable context: data source (CF analytics-engine), privacy (no PII), caching behavior (5min-1h depending on window), and self-aggregating nature. No contradictions.

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 concise (4 sentences) and front-loaded with the most important information (what it returns). Each sentence adds unique value: returns, use cases, data source/privacy, caching. 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?

Given the simplicity of the tool (1 optional parameter, no output schema), the description is complete. It covers purpose, usage, behavioral context, and parameter semantics. The lack of an output schema is acceptable because the description explains the structure of the return ('top tools, top packs, and total call volume') sufficiently.

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% for the single parameter 'window'. The description adds meaning beyond the enum constraints by explaining the effect of window size: shorter windows surface what's hot right now, longer windows show steady-state demand. This helps the agent choose the appropriate value.

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 returns 'top tools, top packs, and total call volume' with specific window options. It distinguishes itself from sibling tools by focusing on trending/call volume data rather than search or entity resolution. The use cases (discovering hot sources, confirming canonical tools, aligning use cases) are specific and actionable.

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 description explicitly provides three use cases for when to use this tool. It does not explicitly state when not to use it, but the sibling list includes many different tools so the context is clear. It lacks explicit alternatives, but the unique nature of the tool (aggregated call signals) makes its usage relatively unambiguous.

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