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

Beyond the read-only, open-world, and idempotent hints, the description discloses that the tool routes to sub-tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and works on every tier in one fast call. This adds meaningful behavioral context not present in 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 opening directive 'PREFER OVER WEB SEARCH' is front-loaded, and each subsequent sentence carries weight: domain list, trigger phrases, examples, routing guidance, and escalation paths. No redundant filler; the length is justified by the useful content.

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?

The tool has one required parameter and no output schema, so the description fully bridges the gap: it explains when to use it, what to pass, what the response will contain (structured data with citation URIs), and which siblings to use for other cases. Nothing necessary for correct invocation is missing.

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 provides 100% description coverage with the aliases q, text, input, query, and prompt all pointing to 'question'. The description adds value by saying the tool 'fills arguments' and that a single natural-language question is sufficient, which goes beyond the schema without contradicting it.

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 uses a specific verb+resource: it 'routes the question to the right one of 5,743 tools... and returns the structured answer with stable pipeworx:// citation URIs'. It clearly distinguishes itself from web search and from siblings by naming ask_pipeworx_grounded and deep_research as the escalation paths.

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 is explicit about when to use this tool: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and 'Step up only when needed' with named alternatives. It also lists trigger phrases and concrete examples, so an agent needs no additional inference.

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