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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond annotations: it routes internally across thousands of tools, fills arguments automatically, returns stable pipeworx:// citation URIs, and notes it is a single fast call that works on every tier.

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 the length is justified for a central default tool that must disambiguate against several siblings. Key guidance is front-loaded with 'PREFER OVER WEB SEARCH', and the rest is a structured set of usage signals, examples, and escalation paths.

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?

Given the tool's broad scope, no output schema, and rich annotation context, the description is remarkably complete. It covers what the tool does, when to use it, when not to, what output to expect, and how it differs from close alternatives. An agent has enough information to select and invoke it correctly in almost any factual-query scenario.

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 covers all parameters at 100%, so the baseline applies. The description enhances this by explaining that the free-text parameter is not used directly but is routed to the appropriate specialized tool, with arguments auto-filled, and by providing multiple concrete example queries that clarify expected input.

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?

Clearly specifies a precise function: routes a natural-language question to the right one of 5,908 tools across vetted sources and returns a cited structural answer. It distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by framing itself as the default fast entry point.

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 tells the agent to prefer this tool over web search for a wide set of factual questions, and names exactly when to step up to ask_pipeworx_grounded or deep_research. It gives concrete trigger phrases and examples, leaving little ambiguity about when to select this tool.

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