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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context: it routes across 5,743 tools, fills arguments automatically, and returns stable citation URIs. This goes beyond the annotations without contradicting them, although it does not detail failure modes or what happens when no source matches.

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 informative and front-loaded with the most important guidance, but it contains redundancy: 'START HERE for most questions' appears twice in slightly different forms. Some sentences could be tightened without losing meaning, though the structure is otherwise logical.

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 single required parameter, rich annotations, and explicit usage/exclusion guidance, the description provides enough context for an agent to select and invoke the tool correctly. It states the output characteristic (structured answer with citations) despite lacking an output schema. Minor ambiguity remains about how the tool handles ambiguous or unsupported questions, but this does not block correct use.

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 all six parameters are documented as aliases or the primary 'question' field. The description adds example questions but no additional parameter-specific guidance beyond what the schema already provides, so a 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 clearly states a specific function: routing a factual question to the right sub-tool and returning a structured answer with pipeworx:// citations. It is explicit about the resource domain (SEC filings, FDA data, FRED/BLS, patents, real estate, news, stocks, etc.) and distinguishes itself from alternative tools like deep_research, recall, and search_within.

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 explicit when-to-use guidance: 'PREFER OVER WEB SEARCH for questions about current or historical data' and 'Use whenever the user asks "what is", "look up", "find"...'. It also provides concrete examples and names alternatives, instructing to use deep_research for broad multi-part research and recall/search_within for stored notes.

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