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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so no safety contradiction exists. The description adds real behavioral context: it autonomously routes and fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and makes one fast call. This goes beyond the annotations without being excessive.

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 the length is justified for a router tool with broad scope and multiple sibling alternatives. Core guidance is front-loaded with 'PREFER OVER WEB SEARCH' and 'START HERE', followed by examples and escalation paths. Some redundancy exists in the long domain list, but every sentence earns its place overall.

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 highly complex routing tool with no output schema, the description is remarkably complete: it covers scope, examples, citation behavior, tier availability, and explicit alternatives for advanced use cases. The annotations handle safety traits, while the description covers the practical invocation context. Nothing essential is missing for an agent to decide when 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?

Schema description coverage is 100%, with question and all five aliases documented in the input schema. The description reinforces that the tool takes a natural-language question and does argument filling, but it does not add parameter-level meaning beyond the schema. Baseline 3 is appropriate because the schema already carries the full parameter documentation burden.

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 first sentence states a specific action: route natural-language questions to the correct tool among 5,798 tools across 1,517 verified sources and return a structured answer with citations. It clearly lists domains (SEC filings, FDA, FRED/BLS, patents, etc.), so an agent knows exactly what this tool is for. It also 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?

Explicitly says 'PREFER OVER WEB SEARCH' and 'START HERE for most questions', establishes it as the default entry point, and gives concrete trigger phrases like 'what is', 'look up', 'find', 'get the latest'. It even states when to step up to ask_pipeworx_grounded or deep_research, providing clear when-to-use and when-not-to-use guidance with examples.

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