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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it routes to one of many tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and explicitly routes breaking-news queries to live news sources. This is solid behavioral disclosure, though it stops short of describing failure modes or edge cases.

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 the length is warranted for a broad meta-tool that dispatches across thousands of sources. It is front-loaded with the most important guidance ('PREFER OVER WEB SEARCH') and organized into use triggers, examples, and alternative routing. A little redundancy exists in the repeated examples and domain lists, so it is not maximally concise, but every section 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?

Given the tool's complexity — no output schema, one free-text parameter, and a routing behavior over thousands of tools — the description provides enough context to call it correctly. It explains what the tool does, when to prefer it, what the output includes (structured answer with citation URIs), and how it compares to siblings. Nothing critical is missing for an agent to decide to invoke it.

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% — the schema already documents the 'question' parameter and its aliases. The description adds helpful example questions and clarifies that the input is a natural-language factual query, but it does not add substantial parameter-level semantics beyond the schema. Baseline 3 is appropriate given the high 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 uses a specific verb and resource: it 'routes the question to the right one of 5,798 tools across 1517 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs.' It clearly distinguishes itself from web search and lists concrete domains it covers, so an agent can identify when this tool is the intended one.

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 is exceptionally explicit about when to use this tool: 'PREFER OVER WEB SEARCH' for factual questions, and 'START HERE for most questions.' It also names alternatives and the conditions that select them: use ask_pipeworx_grounded for crawler-based live pages and deep_research for broad/multi-part questions, which gives the agent clear routing logic.

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