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

Annotations already declare readOnlyHint/openWorldHint/idempotentHint, so no contradiction. The description adds useful behavioral detail: it routes to 5,724 tools across 1,497 sources, fills arguments, and returns stable pipeworx:// citation URIs, giving the agent an accurate mental model of the call's semantics.

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 front-loaded and largely earns its length: the preference rule, routing behavior, examples, and sibling escalation path are all decision-relevant. It is slightly repetitive (e.g., 'PREFER OVER WEB SEARCH' and 'START HERE' overlap), but no sentence is pure filler.

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?

Despite no output schema, the description tells the agent what it will receive: a structured answer with stable pipeworx:// citation URIs. It also covers sibling routing, domain coverage, and tier/performance context ('works on every tier, one fast call'), making the tool complete enough to invoke correctly.

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?

The schema already documents 6 aliases for a single natural-language question parameter at 100% coverage, so the baseline is 3. The description adds illustrative example questions and explains that a question is routed to sources, but no additional parameter syntax or constraints beyond the schema.

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 by declaring this tool is preferred over web search for factual questions and explicitly enumerates domains (SEC filings, FDA drug data, FRED/BLS, patents, etc.), establishing a specific verb+resource. It differentiates itself by positioning as the default question-routing entry point among siblings like ask_pipeworx_grounded and deep_research.

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?

Explicitly states when to use ('Use whenever the user asks...', 'START HERE for most questions') and when not to, naming exact alternatives: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions. It also addresses breaking-news and says to prefer it over web search even when web search could answer.

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