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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description discloses that the signal is self-aggregating from the CF analytics-engine, contains no PII, and is cached for 5 minutes to 1 hour depending on the window. This adds meaningful behavioral context without contradicting any annotations.

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 and front-loaded: opening with the core purpose, then the return value, followed by numbered use cases, and ending with data provenance and caching. Every sentence contributes useful information without fluff, making it both concise and well-organized.

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?

Even though there is no output schema, the description explicitly says what is returned (top tools, top packs, total call volume), plus data source, privacy, and caching behavior. This is complete for a simple read-only tool with one optional parameter, and it fits well within the sibling context.

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 schema already describes the 'window' parameter with enum values and their meaning (shorter windows for hot right now, longer for steady-state). The description adds that caching duration depends on the window, providing extra value beyond the schema, which merits a 4 given the 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 states what the tool does: it reports what other AI agents are calling on Pipeworx, returning top tools, top packs, and total call volume over a recent window. The verb 'returns' plus specific resource and scope make the purpose unambiguous and distinguish it from siblings like discover_tools or ask_pipeworx.

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 provides three explicit 'Useful for' scenarios: discovering hot data sources, confirming canonical tool choice before asking, and checking alignment with common agent needs. This gives clear context, though it doesn't explicitly mention alternatives or when not to use it, so it's just 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.