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 valuable behavioral context: it routes to one of thousands of tools, fills arguments automatically, returns structured answers with stable citation URIs, works on every tier, and makes one fast call. No contradiction with annotations.

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 longer than average but front-loads the most critical guidance (prefer over web search) and every sentence delivers routing or behavioral value. The examples and alternatives are useful rather than filler. Slight redundancy in 'START HERE' and 'default entry point' costs a point but doesn't waste significant space.

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 default entry-point tool with no output schema, the description covers when to use it, what it does, what output to expect (structured answer with citations), what kinds of questions work, and when to switch to siblings. It is complete enough for an agent to invoke it correctly in almost any factual-query scenario.

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 the description already documenting that 'question' accepts aliases like query, q, prompt, text, and input. The description adds general guidance about natural-language questions and fills arguments, but no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 precise function: routes a natural-language question to one of 5,743 tools across 1,500 verified sources and returns a structured answer with pipeworx:// citation URIs. It clearly distinguishes itself from siblings by contrasting with ask_pipeworx_grounded and deep_research, and explicitly frames itself as the default over web search.

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?

Gives explicit when-to-use guidance with trigger phrases ('what is', 'look up', 'get the latest'), specific example questions, and a clear preference hierarchy: prefer over web search, start here for most questions, step up to ask_pipeworx_grounded for verbatim-evidence answers or deep_research for broad multi-part questions. It even addresses breaking-news cases.

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