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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds significant behavioral context: data is 'Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count)' and 'Cached 5min-1h depending on window.' This gives the agent expectations about data source, privacy, and freshness beyond the safety profile.

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 structured with a purpose opening, a concrete 'Returns' statement, and three numbered use cases. Each sentence contributes value, though the opening rhetorical question 'What other AI agents are calling on Pipeworx right now?' is somewhat less crisp than a declarative start. Overall it remains efficient and front-loaded with the return type.

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 no output schema, the description compensates thoroughly by listing the return contents (top tools, top packs, total call volume), the data format (pack, tool, count), the caching behavior, and PII disclosure. This is sufficient for an agent to understand what to expect without ambiguity.

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 input schema fully documents the only parameter 'window' with enum values, a default (24h), and a description of tradeoffs between shorter and longer windows. The tool description merely repeats the enum options without adding new semantic depth, so the baseline of 3 applies due to high schema coverage.

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 specifies the tool's function: 'Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d).' It names a concrete resource (Pipeworx trending usage by other agents) and the specific output, distinguishing it from siblings like discover_tools or recent_alerts.

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 enumerates three use cases: discovering hot data sources, confirming canonical tool choice, and aligning with what most agents need. It also warns about caching ('Cached 5min-1h') which affects freshness expectations. However, it does not name alternative tools or state when not to use it, so it falls short of a 5.

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