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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is established. The description adds meaningful behavioral detail beyond annotations: it routes across 5,743 tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and clarifies that it is not for subjective or speculative questions. 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 front-loaded with the key 'PREFER OVER WEB SEARCH' directive and then organized into categories, examples, and exclusions. It is somewhat long and contains a redundant deep_research instruction ('For broad multi-part...' and 'For questions that need synthesis...' overlap), which keeps it from a perfect score.

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 general routing tool with no output schema, the description is remarkably complete: it defines the input domain, gives example queries, specifies the output shape (structured answer with citation URIs), states when not to use it, and directs the agent to sibling alternatives. Very little is left for the agent to infer.

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 all six parameters documented as aliases of the same natural-language question. The description provides helpful examples of valid questions but does not add parameter-level meaning beyond what the schema already supplies. Baseline 3 is appropriate for full schema coverage.

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: routes a factual question to the right specialized source tool, fills arguments, and returns a structured answer with citation URIs. It clearly separates itself from siblings like ask_pipeworx_grounded and deep_research, so an agent can tell what this tool is for versus the alternatives.

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 an explicit 'PREFER OVER WEB SEARCH' directive, lists the domains it covers, enumerates triggering query phrasings ('what is', 'look up', 'find', etc.), and provides concrete examples. It also states exclusions: not for opinions, predictions, or personal recommendations, and explicitly routes those cases to ask_pipeworx_grounded or deep_research.

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