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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it routes across 5,798 tools, fills arguments automatically, and returns stable pipeworx:// citation URIs. It also sets performance/suitability expectations with 'one fast call' and 'works on every tier', which is useful for tool selection.

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 longer than average, but it is front-loaded with the critical instruction ('PREFER OVER WEB SEARCH') and dense with discriminative information. Examples and explicit sibling comparisons earn their place. Slight redundancy exists between the inline domain list and the examples, but overall the structure supports quick scanning.

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 general-purpose routing tool with no output schema, the description covers the essential context: what types of questions to send, what happens under the hood (routing, argument filling), what the response includes (structured answer + citation URIs), and when to choose a sibling. The absence of error-handling details is acceptable given the tool's broad, open-world nature and the presence of a dedicated grounded alternative.

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%: every parameter is documented as an alias for the natural-language question, and the main 'question' parameter has a clear description. The tool description itself adds no new parameter-level semantics, but examples in the schema illustrate valid inputs. Baseline 3 is appropriate because the schema carries the parameter burden adequately.

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 role: route natural-language factual questions to the right underlying tool and return structured answers with citations. It names the broad domains (SEC, FDA, FRED/BLS, USPTO, ATTOM, weather, clinical trials, stocks, sports, etc.), which makes the tool's purpose concrete. It also explicitly differentiates itself from ask_pipeworx_grounded and deep_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?

The description is unusually explicit about when to use this tool: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and 'works on every tier'. It also names alternatives and the exact conditions for stepping up: ask_pipeworx_grounded for hallucination-resistant single answers, and deep_research for broad/multi-part questions. This gives an agent clear routing logic.

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