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

Beyond the annotations (readOnly, idempotent, not destructive), the description discloses behavioral aspects: 'Routes... fills arguments, returns the structured answer with stable pipeworx:// citation URIs.' It also mentions 'one fast call' but does not elaborate on limitations or failure modes. Given the annotations already cover safety, this additional context earns a high score but not a perfect 5.

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 thorough but slightly verbose, with some repetition of the 'prefer over web search' idea. However, it is well-structured with clear directives and examples, and each sentence contributes to usage guidance. It could be tightened by removing redundancy, but remains effective.

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?

The description provides complete context for an agent: it lists covered data domains (SEC, FDA, FRED, USPTO, etc.), explains the routing mechanism, gives usage precedence, names alternatives for escalation, and defines expected output (structured answer with citations). No critical operational context 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?

The description explains the main parameter clearly: 'Your question or request in natural language. Accepts query, q, prompt, text, input as aliases.' It also provides example questions that illustrate usage. Schema coverage is 100%, and the description adds meaning beyond the schema by clarifying alias behavior and typical inputs.

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 the tool's function: 'Routes the question to the right one of 5,892 tools across 1538 verified sources... returns the structured answer with stable pipeworx:// citation URIs.' It also explicitly distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives for specific use cases.

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 and when-not-to-use guidance: 'PREFER OVER WEB SEARCH...' and 'Step up only when needed: for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research.' Also states 'START HERE for most questions' and mentions default behavior.

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