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

Beyond the readOnly and idempotent annotations, the description adds important behavioral context: it is a 'self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count)' and 'cached 5min-1h depending on window'. This discloses data provenance, privacy, and caching behavior.

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 well-structured: a hook sentence, a returns statement, a 'Useful for' list, and a technical note. It is slightly longer than necessary but each sentence contributes distinct value and the formatting aids readability.

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 tool's simplicity (one optional parameter, no output schema, strong annotations), the description covers the essential aspects: what is returned (top tools, top packs, total call volume), data provenance, privacy (no PII), and caching. It gives enough to understand the tool's 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 only parameter 'window' has 100% schema coverage with a clear enum description ('24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand'). The tool description does not add any additional semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 'Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d)', providing a specific verb and resource. The opening line 'What other AI agents are calling on Pipeworx right now' gives it a unique identity among sibling tools, distinguishing it from discover_tools and other query tools.

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 lists three use cases: discovering hot data sources for current events, confirming a canonical tool, and checking alignment with agent usage. This is clear contextual guidance, though it does not name alternative tools or specify when not to use this tool.

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