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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds meaningful behavioral context: routing across a large tool inventory, filling arguments automatically, returning structured answers, and using stable pipeworx:// citation URIs. No contradiction with 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 front-loaded with a strong preference directive, followed by a scannable category list, concrete routing behavior, and useful example queries. It is dense but every clause contributes meaningful information, with no wasted or redundant sentences.

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 one-required-parameter tool with no output schema, the description is sufficiently complete: it explains what the tool does, what kinds of questions to send, what happens to the question, and what the answer format includes. The examples and coverage list make agent invocation well specified.

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 documents the primary `question` parameter and all five aliases with 100% coverage, so the description does not need to redefine them. It adds example phrasings and trigger words, but no deeper parameter-level semantic detail beyond what the schema already provides.

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 a specific purpose: routes natural-language questions to one of 5,756 tools across 1,504 sources and returns structured answers with citation URIs. It also gives a strong sense of coverage via concrete domains, but it does not distinguish ask_pipeworx from the sibling variants ask_pipeworx_beta and ask_pipeworx_grounded.

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 explicitly says to prefer this tool over web search for factual, current, or historical questions and provides trigger phrases plus examples. It gives clear when-to-use guidance, but it does not mention when to choose sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, and it does not list exclusion cases such as non-factual or creative requests.

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