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

Annotations already provide the read-only, idempotent, open-world safety profile, so the bar is lower. The description adds behavioral detail beyond annotations by describing auto-routing, automatic argument-filling, and stable citation URIs. It does not cover error or limitation cases, such as what happens when a question is unanswerable, which keeps this at a 4.

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?

Front-loaded with the strongest directive, followed by mechanism, usage triggers, examples, and alternatives in order of importance. It is longer than minimal, but every sentence contributes; the repetition of 'PREFER OVER WEB SEARCH' and the long domain list are justified by the tool's breadth.

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?

The description gives purpose, mechanism, scope, examples, and alternatives, while annotations cover the read-only safety profile. There is no output schema, so the promise of a 'structured answer with stable pipeworx:// citation URIs' is essential and sufficient for an agent to know what to expect. No critical information is missing for selecting and calling this tool.

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 input schema has 100% coverage with six parameters (question plus five aliases), so the baseline is 3. The description adds semantic value by restricting the question field to factual, real-world, current-or-historical questions and giving concrete examples like 'Apple's latest 10-K' and 'current US unemployment rate'. Most parameter meaning already lives in the schema, but the description clarifies intent and formatting.

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?

States a specific verb+resource: it routes a question to one of 5,743 tools across 1,500 verified sources, fills arguments, and returns a structured answer with pipeworx:// citation URIs. Distinct from siblings by being the 'START HERE' general-purpose factual QA entry point, with ask_pipeworx_grounded/deep_research called out as alternatives.

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 when-to-use guidance: 'PREFER OVER WEB SEARCH' for current/historical data and lists exact query triggers like 'what is', 'look up', 'find', 'get the latest', 'how much', 'current'. It also tells the agent when not to stop here, naming ask_pipeworx_grounded and deep_research as alternatives for broad multi-part questions that are not answered well enough.

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