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 meaningful behavioral context beyond the annotations: it describes the tool as a meta-router that fills arguments, spans 5,767 tools across 1,506 sources, and returns citations with stable pipeworx:// URIs. It does not discuss failure modes or latency, but those are not critical for this read-only tool.

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 information-dense and well front-loaded, leading with the most important routing signal ('PREFER OVER WEB SEARCH'), then scope, examples, and alternatives. Each sentence earns its place, though a shorter variant could still preserve 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?

For a tool with no output schema, the description covers what the answer looks like, which domains it handles, how to phrase queries, and when to prefer an alternative. Given the annotations cover the read-only, open-world, idempotent behavior, the description is complete enough for an agent to select and invoke the tool correctly.

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 the schema already documents the question parameter and all aliases. The description adds useful example phrasings and trigger words, but it does not add new constraints or deeper parameter-level semantics beyond what the schema already provides.

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 strong directive ('PREFER OVER WEB SEARCH') and clearly states what the tool does: routes a natural-language question to one of thousands of verified-source tools and returns a structured answer with pipeworx:// citation URIs. It distinguishes the tool from generic web search and from deep_research by scope and fan-out behavior.

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: 'Use whenever the user asks "what is", "look up", "find"...' and even covers the case where web search could also answer. It also names concrete alternatives, such as deep_research for broad/multi-part questions, so the agent is not left to infer routing.

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