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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds useful behavioral context: it routes to one of 5,798 tools, fills arguments automatically, returns a structured answer with stable pipeworx:// citation URIs, and handles live news for breaking-news queries. It does not discuss failure modes or the exact response format, so it stops short of a 5.

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 front-loaded and informative, but it is verbose: it lists many domains, includes redundant phrasing such as 'even if web search could also answer it,' and the end segment has formatting artifacts and repetition ('START HERE for most questions. default entry point, works on every tier, one fast call.'). It is useful but not tightly edited.

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 question-routing tool with no output schema, the description covers expected return value (structured answer with citation URIs), concrete question examples, account/tier notes, and when to switch to alternatives. It does not explain fallback/failure behavior or the precise citation format, but it is largely complete for an agent deciding whether and how to call it.

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 documents the required 'question' parameter and all five aliases with 100% coverage, so the description does not need to add parameter-level detail. The description reinforces natural-language usage with examples but provides no new syntactic or semantic information beyond what the schema already states. Baseline 3 applies.

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: answer factual questions over current and historical authoritative data by routing to thousands of verified-source tools and returning structured answers with citations. It explicitly distinguishes itself from web search and from sibling tools like ask_pipeworx_grounded and deep_research, so an agent can tell it apart without opening the schema.

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?

It gives explicit trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current') and says 'START HERE for most questions.' It also provides clear when-not guidance: use ask_pipeworx_grounded for a hallucination-resistant single answer with verbatim evidence, and deep_research for broad/multi-part questions. This is strong routing guidance.

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