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

Beyond the annotations (readOnly, idempotent), the description discloses that data is self-aggregating from CF analytics-engine, contains no PII, and is cached 5min-1h depending on window. This adds behavioral context about freshness and privacy that annotations do not cover.

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 80 words, front-loaded with the core purpose, and uses bullets to organize use cases. Every sentence adds either purpose, output details, use-case guidance, or data provenance, with no filler.

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 read-only trend query with one optional parameter and no output schema, the description covers the return content (top tools, top packs, call volume), the data format (pack, tool, count), staleness, and use cases. This is sufficient for an agent to select and invoke the tool without further documentation.

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 documents the window enum at 100% coverage, but the description adds interpretive meaning: shorter windows surface what's hot right now, longer windows show steady-state demand. It also confirms 24h as default, which is an extra semantic layer beyond the schema.

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 a specific question 'What other AI agents are calling on Pipeworx right now' and clearly states it returns top tools, top packs, and total call volume. This distinguishes it from sibling tools like discover_tools by focusing on aggregate usage trends. The verb 'Returns' and resource are explicit.

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 choices, and checking alignment with agent needs. It also explains window semantics for choosing 24h vs 7d vs 30d. However, it does not explicitly name exclusions or alternatives among siblings, so it falls slightly short of full usage guidance.

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