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

Annotations already declare readOnly=true, openWorld=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds value on top: it routes the question across 5,890 tools, fills arguments automatically, returns a 'structured answer with stable pipeworx:// citation URIs', works on every tier, and is a fast single call. It does not explicitly mention rate limits, quota, or what happens on failed queries, so a 4 rather than a 5, but it conveys behavior that annotations do not.

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 (about 160 words) but linearly front-loaded: the most important guidance ('Prefer over web search') comes first, then scope, routing behavior, using examples, and alternative step-up tools. There is some redundancy (the list of domains is long and constraints 'web search' is repeated), but for a broad router tool the length and structure serve the agent; it is not padded with fluff.

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?

There is no output schema, so the description carries the responsibility of explainable behavior; it does. It states the input (free-form natural language), the process (routes across many internal tools), the output (structured answer with pipeworx:// citation URIs), plus entry-point status, tier behavior, and the edge case for live news. All of that is included, which leaves no missing piece for an agent to correctly invoke the tool.

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?

Parameter schema coverage is 100% — all properties (q, text, input, query, prompt, question) are aliases for the sole `question` parameter and already have clear descriptions. The Tool definition adds no new parameter semantics, it only reinforces the natural-language intent with a few extra examples. This matches the baseline of 3 for fully schema-covered parameters.

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 opens with a clear verb-and-resource: routing questions across 5,890 tools over 1538 verified sources and returning structured answers with stable pipeworx:// citation URIs. It explicitly declares its relationship to web search and to sibling tools (ask_pipeworx_grounded, deep_research), so an agent can immediately tell what it does without opening its schema. The listed domains (SEC filings, FDA data, FRED/BLS, etc.) make the tool's scope concrete and recognizable.

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?

Usage guidance is explicit and prescriptive: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and examples of trigger phrases ('what is', 'look up', 'find', 'get the latest', etc.). It explicitly names the alternatives and the conditions for using them ('for a hallucination-resistant single answer use ask_pipeworx_grounded', 'for broad/multi-part use deep_research'). This is a textbook case of when-to-use / when-not-to-use plus alternative routing.

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