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

Annotations already declare read-only/idempotent/non-destructive; the description adds useful context beyond that: it notes the data is self-aggregating, derived from CF analytics-engine, contains no PII, and is cached 5min-1h depending on window. This gives the agent a clear picture of freshness and privacy without contradicting the 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 compact and structured: what it returns, when to use it, and data caveats. Each of the three sentences earns its place and front-loads the core purpose.

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?

For a simple read-only tool with no output schema, the description explains the return contents (top tools, top packs, total call volume), the data shape ((pack, tool, count)), and freshness/caching behavior. The only minor gap is not detailing exact response formatting, but this is not necessary for selection/invocation.

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 single window parameter is already fully documented in the schema with enum values and semantic guidance ('Shorter windows surface what's hot right now'). The description repeats the window options but adds no additional parameter-specific detail, so the schema handles the load; baseline 3 is appropriate.

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 opens with the interrogative framing 'What other AI agents are calling on Pipeworx right now' and concretely states it returns top tools, top packs, and total call volume over a recent window. This clearly identifies the resource and differentiates 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 includes an explicit 'Useful for' list with three scenarios, such as confirming a canonical tool before asking a question, which gives clear context for when to use it. It does not name alternative tools directly, so it stops short of full when-not-to-use guidance.

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