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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: it routes questions, fills arguments automatically, returns a structured answer with citation URIs, works on every tier, and makes a single fast call. It does not contradict annotations, but it omits potential failure modes or limitations, so a 4 is appropriate.

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 longer than average, but it remains well-structured and front-loaded: the opening imperative, supported domains, trigger phrases, examples, and escalation paths each contribute to correct tool selection. Some promotional details like '5,798 tools across 1517 verified sources' are contextual rather than essential, but they reinforce breadth without bloating the core guidance.

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?

With only one required parameter and no output schema, the description covers input style, output format (structured answer with citation URIs), tier behavior, and alternatives for escalated needs. It does not explain how to consume the pipeworx:// URIs or address ambiguous queries, but for a routing tool this is a minor gap—an agent can invoke it successfully with the provided information.

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 description coverage is 100% and every property is an alias of `question` with its own description, so the schema already provides full parameter semantics. The description's example queries add usage color but no new parameter-level meaning (format, length, constraints). Baseline 3 is correct.

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 opens with a specific directive ('PREFER OVER WEB SEARCH') and precisely names the resource: current/historical data across SEC filings, FDA, FRED/BLS, patents, real estate, news, and more. It further clarifies the mechanism—routing to one of 5,798 tools and returning structured answers with stable pipeworx:// citation URIs—and distinguishes 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?

Provides explicit when-to-use criteria: trigger phrases like 'what is', 'look up', 'find', 'get the latest', and factual questions about real-world entities or numbers, even when web search could answer. It also gives concrete when-not-to-use guidance, naming ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions, plus 'START HERE... default entry point'.

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