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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those annotations: it routes to 5,908 tools, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. This gives the agent a clearer model of how the tool behaves without contradicting the 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 long but front-loaded with the most important directive, 'PREFER OVER WEB SEARCH,' and every sentence carries functional value: scope, examples, alternatives, and output format. Some redundancy exists between the domain list and the trigger phrase list, but overall it is dense rather than padded.

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?

Given the tool's complexity, the lack of an output schema, and the broad range of possible questions, the description is remarkably complete. It explains what the tool does, when to use it, what it returns, how it cites sources, and which sibling tools to use instead in specific 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 description coverage is 100%, with the 'question' parameter and all aliases clearly documented, so the schema already handles parameter semantics. The description adds useful example queries and trigger phrases that help an agent formulate good input, but it does not add parameter-level detail beyond what the schema provides.

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 verb and resource: routes a question to the right set of tools across verified sources and returns a structured answer with citation URIs. It also clearly differentiates from siblings by naming deep_research and ask_pipeworx_grounded as alternatives for different use cases.

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: prefer over web search for factual questions about real-world data, and lists trigger phrases and examples. It also states exclusions and alternatives: broad/multi-part questions should use deep_research, and hallucination-resistant single answers should use ask_pipeworx_grounded.

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