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

Annotations already cover read-only, open-world, idempotent, and non-destructive safety. The description adds meaningful behavioral detail: it routes across thousands of tools, fills arguments automatically, and returns structured answers with stable citation URIs. It does not mention limitations or failure modes, but the annotations carry the main safety burden.

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 most important instruction ('PREFER OVER WEB SEARCH') and is organized into scope, behavior, usage triggers, examples, and sibling routing. It is longer than strictly necessary and somewhat repetitive about web search preference, but every major sentence contributes to agent decision-making.

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 simple one-parameter tool with rich annotations and simple schema, the description provides enough context to invoke it correctly: when to use it, what it returns, and where to route complex queries. It does not differentiate ask_pipeworx_beta or ask_pipeworx_grounded, but the core usage is fully specified.

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?

The schema already documents the single 'question' parameter and its aliases at 100% coverage. The description goes beyond the schema by providing trigger verbs and six concrete example questions, which help the agent understand the expected phrasing and scope. No additional formatting constraints are needed.

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 precise action: it routes a natural-language question to one of 5,743 tools, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. It clearly distinguishes itself from generic web search and names relevant alternatives like deep_research, while the example domains make its scope unmistakable.

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 explicitly says to prefer this tool over web search, lists trigger phrases such as 'look up' and 'get the latest', and explicitly routes broad multi-part questions to deep_research. This gives an agent clear conditions for choosing this tool over alternatives.

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