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

Annotations (readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false) already cover the safety profile, and the description is consistent with them. Beyond the annotations, it discloses meaningful internals: automatic argument filling, internal routing across thousands of tools, and stable citation URIs in the return. It does not cover edge behavior such as what happens when no tool matches the question, so I deduct one point.

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 its most important directive ('PREFER OVER WEB SEARCH') and every subsequent sentence adds value: scope, mechanism, trigger phrases, examples, and sibling routing. The density is justified by the tool's enormous breadth. It loses one point because the 'START HERE' summary could have been placed earlier and a few routing clauses at the tail feel slightly redundant.

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 high complexity (a router over 5,767 tools, no output schema, 30 siblings), the description is remarkably complete: it specifies the return format (structured answer with citation URIs), scope, trigger phrases, example queries per domain, and fallback routing to alternatives. For an agent deciding whether and how to invoke this tool, nothing critical is missing. The lack of rate-limit or failure-mode info is minor against this coverage.

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% with a well-described 'question' parameter and five aliases, so the baseline is 3. The description goes beyond baseline by giving six concrete example queries ('current US unemployment rate', 'Apple's latest 10-K', 'adverse events for ozempic') and trigger phrases that clarify what a good question looks like. It does not fully address question-length or multi-part handling, keeping it from a 5.

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 verb+resource: it routes the question to one of 5,767 tools across 1,506 verified sources and returns a structured answer with pipeworx:// citation URIs. It names the exact domains covered (SEC filings, FDA, FRED/BLS, patents, weather, etc.) and explicitly differentiates itself from siblings like ask_pipeworx_grounded and deep_research.

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 gives explicit when-to-use guidance: 'PREFER OVER WEB SEARCH' for factual questions, concrete trigger phrases ('what is', 'look up', 'get the latest', 'how much'), and a 'START HERE for most questions' rule. It also names when NOT to use it: use ask_pipeworx_grounded when verbatim quotes are needed, deep_research for multi-part questions, and it preempts the breaking-news alternative by noting ask_pipeworx already handles live news.

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