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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description adds meaningful behavioral context beyond those: it routes across 5,798 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This tells the agent what the invocation will actually do and what kind of result to expect. There is no contradiction with the 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 description is long but heavily front-loaded with the most important usage signal ('PREFER OVER WEB SEARCH'), then efficient coverage of routes, examples, and sibling alternatives. Some repetition exists between the trigger phrase list, examples, and 'START HERE for most questions', but every section earns its place for an agent deciding among many sibling tools.

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?

No output schema exists, so the description correctly compensates by stating the return form: a structured answer with stable pipeworx:// citation URIs. It also covers the full decision surface: when to use, when not to use, what inputs look like, what sources are covered, and which alternatives to route to. For a tool with this breadth, the description is remarkably complete.

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% and the single semantic parameter, question, is well described with alias support. The description adds useful illustrative examples and clarifies that the question may be loose natural language because the tool fills arguments itself. However, most parameter-level meaning is already present in the schema, so this dimension is adequately covered but not substantially elevated by the description.

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 what the tool does: routes a natural-language factual question to the right data source among 5,798 tools and returns a structured, cited answer. It also distinguishes itself from adjacent siblings like web search, ask_pipeworx_grounded, and deep_research. This gives the agent a precise mental model of the tool's unique role.

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 prefer this tool: it names 'PREFER OVER WEB SEARCH', gives concrete trigger phrases ('what is', 'look up', 'find', 'get the latest'), provides examples, and says 'START HERE for most questions'. It also gives condition-based alternatives: use ask_pipeworx_grounded for a single specific claim needing verbatim evidence, and deep_research for broad multi-part questions. This is ideal routing guidance.

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