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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it explains that the tool routes internally, fills arguments automatically, and returns structured answers with citation URIs. It doesn't mention rate limits or auth, but with annotations covering safety, the disclosure is sufficient.

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 front-loaded with the most important guidance ('PREFER OVER WEB SEARCH') and every sentence adds value: trigger phrases, examples, routing behavior, citation output, and alternative tools. It is structured and scannable, though slightly verbose.

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 that there is no output schema, the description adequately explains the return format ('structured answer with stable pipeworx:// citation URIs') and covers a wide range of use cases with examples and alternatives. It doesn't describe failure modes, pagination, or limits, but for a broad router tool with strong annotations, this is a minor gap.

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 single required parameter is fully documented, including alias fields. The description reinforces that input is a natural-language question and gives example phrasings, but it does not add substantial meaning 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 states exactly what the tool does with a specific verb and resource: it routes a natural-language question to the right one of 5,798 tools across 1,517 sources and returns a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from named siblings like ask_pipeworx_grounded and deep_research, so an agent can tell them apart.

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 is explicit about when to use this tool versus alternatives: it says to prefer it over web search, gives trigger phrases ('what is', 'look up', 'find', etc.), provides concrete examples, and names specific alternatives with conditions ('hallucination-resistant single answer... use ask_pipeworx_grounded'; 'broad/multi-part question... use deep_research').

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