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

Annotations already declare readOnly/openWorld/idempotent, and the description adds meaningful behavioral context: it routes dynamically across thousands of tools, fills arguments, returns structured answers with stable citation URIs, and handles breaking-news queries. There is no contradiction with annotations, and the agent gets an accurate model of what happens when the tool is invoked.

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 instruction ('PREFER OVER WEB SEARCH') and organized into domain list, routing behavior, trigger phrases, and examples. Some redundancy exists between 'even if web search could also answer' and 'START HERE for most questions,' but the length is largely justified by the tool's broad scope.

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 routing tool with one required natural-language parameter and no output schema, the description covers function, routing behavior, citation output, triggering conditions, and representative examples. An agent has enough information to decide when to call it and what to pass.

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 explains the natural-language 'question' parameter and its aliases. The description contributes useful example queries and notes that the tool 'fills arguments', but it does not add per-parameter meaning beyond what the schema provides, so the baseline 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 states a specific action ('routes the question to the right one of 5,798 tools... returns the structured answer with stable pipeworx:// citation URIs') and clearly names the resource and scope. It also differentiates the tool from web search and signals it is the umbrella entry point ('START HERE'), which separates it from specialized sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded.

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?

It gives explicit when-to-use guidance ('PREFER OVER WEB SEARCH', 'Use whenever the user asks...'), concrete example triggers, and names the main alternative (web search). It lacks an explicit when-not-to-use or a direct comparison with sibling variants like ask_pipeworx_grounded/beta, so it is clear but not exhaustive.

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