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

The description discloses meaningful behavior beyond the annotations: it routes internally across 5,743 tools, fills arguments, and returns answers with stable pipeworx:// citation URIs. No contradiction with the readOnlyHint/openWorldHint/idempotentHint annotations; only minor caveats like latency or failure modes are omitted.

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 key guidance is front-loaded and useful, but the description becomes highly repetitive: the same example list and 'START HERE for most questions' sentence are repeated multiple times. This is significant redundancy that reduces the clarity of the tool definition.

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 natural-language router tool, the description covers when to use it, how to phrase input, what it does internally, and what kind of output to expect. It is complete enough for an agent to invoke correctly, though explicit differentiation from sibling ask_pipeworx tools would make it more robust.

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 schema already documents that question accepts natural language and that q, text, input, query, and prompt are aliases. The description reinforces this with examples but adds no additional parameter-level semantics 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 clearly states that ask_pipeworx routes natural-language factual questions to specialized tools, fills arguments, and returns structured answers with citation URIs. It is well-scoped against web search, but it does not explicitly distinguish itself from sibling variants like ask_pipeworx_grounded or ask_pipeworx_beta.

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?

It gives explicit guidance to prefer this tool over web search, says 'START HERE for most questions,' lists trigger phrases, and provides concrete examples. It lacks any when-not-to-use guidance or routing rules among the sibling ask_pipeworx variants and deep_research.

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