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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds valuable behavioral context: it routes across thousands of sources, fills arguments, returns structured answers with pipeworx:// citation URIs, and is described as 'one fast call'. It doesn't cover rate limits or failure modes, but the annotation coverage lowers the burden and it adds meaningful beyond-schema context.

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 every sentence earns its place: it provides domain coverage, query patterns, examples, and alternative tools. Some redundancy exists between 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', and phrases like 'works on every tier, one fast call' add minor promotional value. Still, the structure is logical and front-loaded with the most important usage guidance.

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?

Despite having no output schema, the description explains what the tool returns: structured answers with stable pipeworx:// citation URIs. It covers scope, routing behavior, domain coverage, alternatives, and examples. Given the tool's simplicity (one natural-language parameter) and rich annotations, nothing critical is missing for an agent to invoke it correctly.

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 description coverage is 100% because the single required parameter 'question' and its five aliases are all documented. The description provides natural language query guidance and examples but doesn't add deeper semantics beyond what the schema already states. Baseline 3 is appropriate since the schema fully documents the parameter.

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 'routes the question to the right one of 5,724 tools...' and clearly identifies the resource and scope: authoritative structured data with citations. It distinguishes itself from siblings by explicitly naming ask_pipeworx_grounded and deep_research as different alternatives. The use cases and examples make the tool's function unmistakable.

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 'PREFER OVER WEB SEARCH' and gives a clear list of domains and query patterns that should route here. It also provides step-up guidance: use ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions. This is exemplary when-to-use versus when-not-to-use guidance.

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