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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond annotations: it routes to the right tool among thousands, fills arguments, returns stable citation URIs, works on every tier, and is a single fast call. It does not contradict the annotations and supplies additional operational expectations.

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 well-structured and front-loaded with the most important usage directive. The examples and sibling routing guidance are valuable; the extensive category list ('SEC filings, FDA drug data, ...') is somewhat redundant with the examples but still reinforces the tool's broad scope. Overall, each section earns its place and the key message is immediate.

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 one required parameter, no output schema, and read-only/idempotent annotations, the description is complete. It tells the agent when to use it, when not to, what it returns (structured answers with citation URIs), provides concrete examples, and distinguishes it from relevant siblings. Nothing needed for correct selection or invocation is missing.

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 coverage is 100%: the schema documents 'question' and all five aliases (q, text, input, query, prompt). The description does not add new parameter-specific semantics, just examples of acceptable questions. This meets the baseline-3 expectation when the schema carries the parameter documentation burden.

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 specific directive ('PREFER OVER WEB SEARCH') and clearly states the tool's function: routes questions to one of 5,743 tools across 1,500 verified sources and returns structured answers with pipeworx:// citation URIs. It names concrete domains and example queries, making the tool's purpose unmistakable and distinct from general web search.

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 when to prefer this tool over web search, provides trigger phrases ('what is', 'look up', 'find', 'get the latest'), and gives examples. It also differentiates from siblings: use ask_pipeworx_grounded for hallucination-resistant single answers, deep_research for broad/multi-part questions, and this tool for breaking news already routed to live news feeds.

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