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

Beyond the readOnly and idempotent hints, the description adds key behavioral context: it is 'derived from CF analytics-engine, no PII, just (pack, tool, count)' and is 'Cached 5min-1h depending on window.' This discloses data provenance, privacy, and caching behavior, which is valuable for an agent deciding whether to trust/call the tool.

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 about four sentences with a clear front-loaded purpose, followed by a compact numbered list of use cases. Every sentence earns its place, covering return values, use cases, data source, privacy, and caching without fluff.

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 tool with one optional parameter and no output schema, the description covers the return value ('top tools, top packs, and total call volume'), the shape ('(pack, tool, count)'), caching, and use-case context. It is sufficiently complete for an agent to invoke correctly.

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' is fully described in the schema with enum values and semantics ('Shorter windows surface what's hot right now; longer windows show steady-state demand'). The tool description adds nothing beyond that, so the schema does the heavy lifting and a 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 'What other AI agents are calling on Pipeworx right now' and explicitly states it 'Returns the top tools, top packs, and total call volume over a recent window', making the verb+resource clear. This distinguishes it from sibling tools like discover_tools by focusing on live usage trends rather than static discovery.

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, giving clear guidance on when to use the tool. However, it does not mention alternatives or exclusions, such as how it differs from discover_tools or when not to use it, so it stops short of full differentiation.

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