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

Beyond readOnly/openWorld/idempotent annotations, the description discloses routing behavior, argument filling, stable pipeworx:// citation URIs, and 'one fast call' performance. It does not mention failure modes or rate limits, but the additional behavioral context is meaningful.

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 front-loaded with the most important guidance and organized into usage rules, examples, and escalation paths. Some redundancy exists between the trigger-phrase guidance and examples, but each section earns its place for such a broad default tool.

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?

Even without an output schema, the description tells the agent what to expect (structured answer with citation URIs), which domains are covered, when to prefer alternatives, and provides concrete invocation examples. This is sufficiently complete for correct selection and use.

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 coverage is 100%, and all parameters are documented as aliases of the same 'question' field. The description reinforces this with natural-language examples but does not add significant new semantic constraints beyond what the schema already provides.

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 clear purpose: route factual questions to one of 6,032 verified-source tools and return cited structured answers. It explicitly positions the tool as the default entry point over web search and distinguishes it from grounded and deep-research siblings.

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?

Gives explicit guidance: 'PREFER OVER WEB SEARCH', trigger phrases like 'what is' / 'look up' / 'current', concrete examples, and a hierarchy ('START HERE', 'Step up only when needed') with named alternatives ask_pipeworx_grounded and deep_research.

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