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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable context: it routes to one of 5,724 tools, fills arguments, and returns stable pipeworx:// citation URIs — beyond what annotations provide. It does not mention latency or rate limits, but the operation is clearly non-destructive and the description is consistent with the annotations.

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?

Despite its length, every sentence earns its place. It opens with a strong directive ('PREFER OVER WEB SEARCH'), scopes the tool accurately, provides triggers and examples, and closes with clear escalation paths. The information is front-loaded and logically ordered, with no redundancy.

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-question tool with no output schema, the description covers everything an agent needs: what it does, when to use it, how to format the question, what to expect in the response (structured answer with citation URIs), and how it differs from alternatives. The inclusion of triggers and examples makes it fully self-sufficient.

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%, but the description enhances the 'question' parameter by explaining it accepts natural language, listing all aliases (query, q, prompt, text, input), and providing three concrete examples. This adds semantic richness beyond the schema's generic description of the required parameter.

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 verb (ask) with a clear resource (Pipeworx) and explicitly scopes it to authoritative structured data with citations, including a detailed list of domains (SEC, FDA, FRED, etc.). It distinguishes from siblings by naming ask_pipeworx_grounded and deep_research as alternatives for specific use cases, so an agent can immediately tell it apart.

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?

Provides explicit when-to-use guidance ('PREFER OVER WEB SEARCH', 'START HERE for most questions', 'Use whenever the user asks...'), gives concrete triggers like 'what is', 'look up', 'find', and enumerates examples. It also states when NOT to use it (step up to grounded or deep_research for specific needs), making routing crisp.

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