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

Beyond the readOnly/openWorld/idempotent/destructive annotations, the description adds rich behavioral detail: parallel decomposition across 5,724 tools, findings packet with verbatim evidence + confidence + source + fetched_at, explicit gaps[] for unanswered facets (never invents), contradictions[] scan, hop fields, citation_uri resolvability, large-record excerpting, and latency expectations (15-90s). No contradiction with annotations; it substantially expands the safety and execution profile.

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 (~300 words) but dense; it front-loads the account requirement and core distinction from open-web search, and organizes content logically (what, when, depth semantics, behavioral details). Every sentence carries informative weight; it could be slightly tighter around depth repetition, but it remains well-structured and readable.

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 no output schema, the description thoroughly describes the returned artifacts (findings packet with verbatim evidence, confidence, source, fetched_at, citation_uri, gaps[], contradictions[]), plus depth variations, latency, and prerequisites. An agent has all needed context to invoke it correctly and interpret results.

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% — both question and depth are already documented in the schema (depth lists enum values and their exact behaviors, question says 'natural language'). The description adds example phrases for question and mentions 'standard' is default, but these are already present in the schema. It adds no significant new parameter meaning 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 states a specific verb-resource combo: 'Grounded multi-source research across Pipeworx's 1497 STRUCTURED data sources' and explicitly contrasts with open-web search ('this is NOT open-web search'). It names the sibling ask_pipeworx and explains the difference, making the tool's purpose unmistakable even without opening the schema.

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 ('Best for broad/multi-part questions over structured data') and when-not-to-use ('For BREAKING or colloquial CURRENT-NEWS... prefer ask_pipeworx'; 'For a single lookup use ask_pipeworx'). It also states the account prerequisite and that ask_pipeworx works on every tier, covering both selection and access notes.

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