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

The annotations already declare readOnly/openWorld/idempotent, and the description adds materially beyond them: it decomposes into facets, routes to 5,798 tools in parallel, returns gaps[] rather than inventing answers, returns fetchable pipeworx:// citation URIs only when resolvable, semantically excerpts long records, and gives latency expectations. No statement contradicts 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?

The description is information-dense and does front-load the account requirement, but it is a single long block of text with extensive parentheticals and some redundancy, e.g. the depth mechanics repeat and overlap with the schema's enum descriptions. It could be tightened with structured bullets without losing value.

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 complex research tool with no output schema, the description is complete: it covers auth and tiers, target use case vs alternatives, input expectations, output packet contents, gaps/citations/contradictions behavior, excerpting, and runtime. An agent has enough context to select the tool and call it with correct expectations.

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 covers both parameters at 100% and describes the depth enum in detail, so the baseline is 3. The description adds genuine extra semantics for depth by explaining what 'standard' and 'thorough' actually do (re-angle unanswered gaps, chase leads, contradictions scan) and confirms that broad/multi-part questions are acceptable for the question 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 opens with the core operation: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources ... in ONE call' and explicitly says it is not open-web search. It also identifies the intended question type — 'broad/multi-part questions over structured data' — and contrasts with 'For a single lookup use ask_pipeworx,' so the tool separates cleanly from its siblings.

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?

Use is scoped explicitly: it is 'Best for broad/multi-part questions over structured data,' while single lookups are routed to ask_pipeworx. It also states the account prerequisite, the paid requirement for 'thorough', and 'If you are not signed in, use ask_pipeworx instead.' This is much stronger than an implied usage hint.

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