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

Annotations already mark this as readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral context: it routes and fills arguments on the agent's behalf, returns structured answers with citation URIs, and makes 'one fast call' on every tier. This goes beyond the annotations without contradicting them.

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 directive and organized into use-when, examples, default status, and escalation paths. There is some redundancy between the 'Use whenever' list and the example questions, but every section serves a distinct routing purpose.

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, open-ended question-answering tool with no output schema, this description is complete: it covers scope, examples, alternatives, return format, citation URIs, tier availability, and speed. An agent has enough context to select and invoke the tool correctly in most factual-question scenarios.

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%: all six parameters are aliases for the required 'question' string, and the schema clearly describes natural-language input. The description contributes examples and query-phrase patterns but doesn't add new parameter-level semantics, so the baseline score of 3 is appropriate.

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 states the core function: routes a natural-language question to the appropriate tool among 5,743 sources and returns a structured answer with stable pipeworx:// citation URIs. It also distinguishes itself from siblings like ask_pipeworx_grounded and deep_research by positioning itself as the default entry point.

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 lists concrete example questions. It also names the conditions for escalating to ask_pipeworx_grounded and deep_research, plus how ask_pipeworx handles breaking-news queries.

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