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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context beyond those hints: it routes internally to 5,724 tools, fills arguments, returns a structured answer with stable pipeworx:// citation URIs, and positions itself as the fast, default entry point. This meaningfully expands beyond the annotation hints, though it does not 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 long but exceptionally dense with actionable routing guidance. It front-loads the most important instruction ('PREFER OVER WEB SEARCH'), then organizes by source categories, trigger phrases, examples, and alternatives. A small amount of redundancy exists between the trigger-phrase list and the examples, but every sentence contributes to selection and invocation.

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 single-parameter router tool with no output schema, the description is highly complete: it tells the agent what the tool does, what inputs are acceptable, what output to expect (structured answer with citation URIs), when to choose it over web search, when to prefer sibling tools, and how it handles breaking-news queries. No significant guidance gap remains.

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% and the schema already documents the single required parameter and all aliases clearly. The description reinforces the natural-language nature of the input with examples and trigger phrases, but it adds no new parameter-specific semantics beyond what the schema already provides, so the baseline score of 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 specific purpose: answering factual questions about current or historical real-world data by routing to one of 5,724 tools across 1,497 verified sources and returning structured answers with citation URIs. It also distinguishes itself from siblings by contrasting with ask_pipeworx_grounded and deep_research, making the tool's scope and selection clear.

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 over web search for factual questions, provides trigger phrases ('what is', 'look up', 'get the latest'), gives concrete examples, and names the alternatives with the conditions for stepping up: ask_pipeworx_grounded for hallucination-resistant verbatim evidence, deep_research for broad/multi-part fan-out. This gives an agent clear when-to-use and when-not-to-use guidance.

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