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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds routing behavior, the scale of the tool set, stable citation URIs, and the 'one fast call' latency claim. It does not fully disclose edge-case behavior such as no-match answers, but given the strong annotations this is not a serious gap.

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?

Dense but front-loaded with the most important routing instruction. The domain list, examples, and alternatives all earn their place, though the six examples plus schema examples make it slightly longer than strictly necessary.

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 broad default router with no output schema, the description covers source domains, return shape, citation format, tier/performance, examples, and escalation paths. It is arguably missing an explicit 'when not to use' hedge, but for an initial entry point it is close to complete.

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 all six aliases documented, so the baseline is 3. The description adds value by clarifying that the input is a natural-language question and by giving representative real-world prompts that show expected granularity, so it earns a 4.

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 an explicit routing job: takes a natural-language question, chooses one of 5,743 tools across 1,500 sources, fills arguments, and returns a structured answer with pipeworx:// citations. This is much more specific than the title and distinguishes it from the grounded and deep_research siblings.

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?

Opens with PREFER OVER WEB SEARCH, lists trigger phrases like 'what is', 'look up', 'find', 'get the latest', and 'current', provides six concrete examples, declares it the default START HERE, and explicitly says to step up to ask_pipeworx_grounded or deep_research only in named conditions. When-not-to-use is clearly covered.

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