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

Annotations already cover safety (read-only, idempotent, non-destructive, open-world). The description adds meaningful behavior beyond those annotations: it routes the query across 5,798 tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and handles breaking news via news packs. It doesn't discuss latency/cost/auth, but that is minor given the annotation coverage.

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 long but front-loaded and well-organized: priority statement first, then scope, mechanics, trigger phrases, examples, and routing alternatives. Almost every sentence contributes decision-relevant guidance; only the list of example queries is slightly redundant with the domain list.

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 tool with a single free-form question parameter, no output schema, and rich annotations, the description is largely complete: it explains inputs, outputs (citations), scope, and alternatives. It does not mention the ask_pipeworx_beta sibling or any limits on question length/source availability, but these are not critical for the primary call path.

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?

Schema coverage is 100% and the sole meaningful parameter (question) is already described as accepting aliases. The description adds examples and trigger phrases that clarify acceptable phrasing, but it doesn't add new parameter-level semantics beyond the schema, so the baseline of 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 states a specific, actionable purpose: ask_pipeworx routes a factual question to the right source tool and returns a structured answer with stable pipeworx:// citation URIs. It also explicitly contrasts itself with web search and sibling tools like ask_pipeworx_grounded and deep_research, so an agent can distinguish it immediately.

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?

Usage guidance is explicit and rich: it lists the domain categories, provides trigger phrases and examples, and says 'START HERE for most questions'. It names alternatives for grounded-only mode (ask_pipeworx_grounded) and broad multi-part research (deep_research), covering both when and when-not to use this tool.

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