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

The annotations already establish read-only, open-world, idempotent behavior, so the description's main value is its extra routing behavior: it auto-selects from 5,798 tools, fills in arguments, and returns structured answers with stable pipeworx:// citation URIs. That adds meaningful transparency beyond the annotations, though it doesn't discuss failure modes or rate limits.

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 relatively long but front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and densely packed with useful routing and examples. Some repetition exists between the source list and trigger phrases, but nearly every sentence earns its place.

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 tool with no output schema and a very broad routing responsibility, the description explains the return format (structured answer with citation URIs) and provides enough alternative routing to orient the agent. It could mention failure/handoff behavior when the question doesn't match any source, but overall it is sufficiently complete.

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 fully explained and all aliases documented. The description gives examples of valid questions but doesn't really add parameter-level semantics beyond what the schema already provides. 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 clear, specific purpose: prefer this tool over web search for current or historical factual data across a long list of source types, and it routes the question to the appropriate sub-tool. It also explicitly differentiates itself from siblings like ask_pipeworx_grounded and deep_research, so an agent can distinguish it without opening schemas.

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 unusually explicit when-to-use guidance: trigger phrases like 'what is', 'look up', 'get the latest', plus concrete examples. It also names alternatives and their conditions: use ask_pipeworx_grounded for fact-driven research and deep_research for broad multi-part questions. This is strong, actionable routing.

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