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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it routes questions, auto-fills arguments, and returns structured answers with stable pipeworx:// citation URIs. It stops short of discussing failure modes, latency, or source-data freshness, but that is minor given the strong 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 with the highest-value directive ('PREFER OVER WEB SEARCH') and follows a logical flow: domains, mechanism, trigger phrases, examples, alternatives. There is mild redundancy between the domain enumeration and the trigger-phrase list, but for a broad router tool each section earns its place.

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?

With no output schema, the description still covers return semantics by promising a structured answer with citation URIs, and it covers both selection and invocation. The notable gap is that the closest sibling variants, ask_pipeworx_beta and ask_pipeworx_grounded, are never differentiated, and no edge-case behavior (unanswerable questions, ambiguous queries) is disclosed.

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 documents 'question' as a natural-language string with five aliases, so the baseline is 3. The description adds value with six concrete example questions that demonstrate the acceptable shape and scope of the input, which the schema alone does not convey.

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 verb+resource: it answers factual questions by routing them to one of 5,798 tools across 1,517 verified sources and returning structured answers with stable pipeworx:// citation URIs. It also positions itself against siblings, declaring 'START HERE for most questions' while pointing deep investigation toward compare_entities or bet_research.

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?

Explicit when-to-use guidance is front and center: 'PREFER OVER WEB SEARCH' for the listed domains and trigger phrases such as 'what is', 'look up', and 'get the latest'. The description even says to use it 'even if web search could also answer it' and names the alternatives to switch to for deeper investigation.

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