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

Annotations already indicate a safe read-only operation, and the description adds meaningful behavioral detail: it routes to one of 5,743 verified-source tools, fills arguments, returns stable pipeworx:// citation URIs, and is described as one fast call working on every tier. No contradiction with the readOnly/openWorld/idempotent 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 earns most of its length: it front-loads the 'prefer over web search' directive, enumerates coverage areas, gives examples, and explains the escalation path to siblings. Minor redundancy exists ('START HERE' and 'default entry point' say the same thing), but no filler dominates.

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 broad query-routing tool with no output schema, the description is remarkably complete: it covers what it returns (structured answer with citation URIs), when to use it, when to escalate to named siblings, what kinds of questions work, and even confirms news coverage. An agent has enough context to select and invoke this tool 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 coverage is 100% and the schema already documents the six aliases (q, text, input, query, prompt, question) clearly. The description adds helpful examples and question-shape guidance, but does not need to add parameter semantics because the schema carries that weight.

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 precise purpose: routing factual questions about authoritative/structured data to the correct among 5,743 tools and returning structured answers with citation URIs. It also clearly distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as the alternatives rather than being confused with them.

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?

Explicitly says to prefer it over web search and gives concrete trigger phrases ('what is', 'look up', 'find', 'get the latest', etc.). It also states when NOT to use it: step up to ask_pipeworx_grounded for hallucination-resistant single answers or deep_research for broad/multi-part questions, and it mentions that news/breaking-news is already covered.

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