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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive traits. The description adds meaningful behavioral context: it routes to one of 5,798 tools, fills arguments automatically, and returns structured answers with stable citation URIs. This reveals the delegation mechanism and output format beyond what annotations state. It does not discuss rate limits or failure modes, but that is not critical given the safety 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 well-organized with a strong lead ('PREFER OVER WEB SEARCH'), a behavior summary, trigger phrases, and examples. However, it contains redundancy: 'even if web search could also answer it' appears twice, and the final 'START HERE' instruction repeats the opening preference over web search. The list of domains and examples is useful, but the text could be tightened without losing meaning.

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 tool's complexity as a natural-language router and the absence of an output schema, the description covers the key aspects: what inputs to provide, when to prefer this tool, how the routing works, and what kind of response to expect (structured answer with citation URIs). It does not explain differences from similar sibling tools, but the provided guidance is sufficient for most factual questions.

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 fully documents all parameters (all aliases for 'question' at 100% coverage), so the baseline is 3. The description adds value by supplying concrete example queries ('current US unemployment rate', 'Apple's latest 10-K', 'active clinical trials for GLP-1') that illustrate the expected formatting and content of the natural-language question parameter. This goes slightly beyond the generic schema description.

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 a specific function: it routes a natural-language question to the right data source among 5,798 tools across 1,517 verified sources and returns a structured answer with pipeworx:// citation URIs. It explicitly lists domains (SEC filings, FDA data, economic statistics, etc.) and provides concrete examples, making the tool's purpose unmistakable. It also distinguishes itself from web search without relying on name alone.

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' and 'Use whenever the user asks...' with trigger phrases like 'what is', 'look up', 'find', and 'current'. It clarifies that even if web search could answer, this tool is preferred. However, it does not mention sibling alternatives such as ask_pipeworx_beta, ask_pipeworx_grounded, or deep_research, so an agent must infer when those should be used instead.

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