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, and the description is fully consistent with them — no contradiction. The description adds value beyond annotations by disclosing that it auto-routes and fills arguments on the agent's behalf and that answers carry citation URIs. It doesn't mention rate limits, latency, or failure modes, but the annotation coverage lowers the bar.

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 well front-loaded — the headline decision, domain list, and triggers come first — but the later paragraphs repeat sibling-routing advice (ask_pipeworx_grounded and deep_research are each introduced twice) and the sentence 'step up only when needed' is awkwardly worded. It is informative but could be tightened by ~20-30% without losing content.

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 high-complexity tool with no output schema, the description covers scope, trigger phrases, exclusions, sibling routing, and return format (structured answer with citation URIs). Minor gaps: what happens when routing finds no source, response format details, and any limits are unspecified. These are secondary given the strong usage guidance.

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%: the question parameter is described and all five aliases (q, text, input, query, prompt) are labeled 'Alias for question.' The description adds trigger phrases and examples that inform how to phrase queries, but no parameter-level detail beyond the schema. Baseline 3 applies since the schema does the heavy lifting.

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 a specific verb+resource: it routes a natural-language question to the right one of 5,798 tools across 1,517 verified sources and returns a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from siblings explicitly (ask_pipeworx_grounded for reasoning over retrieved documents, deep_research for fan-out, web_search for ordinary browsing), so an agent can tell it apart without opening schemas.

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 unusually explicit: it front-loads 'PREFER OVER WEB SEARCH,' lists concrete trigger phrases and domains, gives six examples, states exclusions ('Do NOT use for: casual/general web browsing, image search, social media posts'), and routes to named alternatives for specific conditions (grounded reasoning, multi-part fan-out). Little is left to inference.

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