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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context: it decomposes questions into facets, routes to 5,798 tools in parallel, returns a findings packet with verbatim evidence + confidence + source + fetched_at + stable pipeworx:// citation, never invents gaps, and explains the second-hop iteration with gap recovery. It also discloses latency (15-60s, thorough up to ~90s) and the condition under which citation_uri appears. A small deduction because not all edge behaviors (e.g., what happens on rate limits) are disclosed, but this is rich beyond 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 long (roughly 220 words) but every sentence earns its place: it covers the account requirement, alternatives, the research mechanism, outputs, depth semantics, gaps, latency, and citation behavior. It is front-loaded with the most critical gate (account required/sign in) and the key differentiator (structured data, not open-web). It loses a point for density and length, which could be trimmed by moving some detail to the schema, but it remains 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 2-parameter tool with 100% schema coverage and no output schema, the description is exceptionally complete: it explains what the tool returns (findings packet with verbatim evidence, confidence, source, fetched_at, pipeworx:// citation), how it handles gaps (gaps[] never invented), how depth levels iterate, when citations are fetchable, and how long the call takes. Given the tool's complexity, the description covers all the context an agent needs to decide when and how to call it. The only minor gap is no explicit mention of the exact output structure beyond prose, but for an agent the prose is 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%, so the baseline is 3. The description adds meaningful semantics beyond the schema: it clarifies that depth:'standard' is the default (schema says standard=3, default; description confirms and explains the gap-recovery hop), and it explains that depth:'thorough' is paid and requires a paid plan, which is not in the schema. It also gives a behavioral sense of depth:'quick' as single-hop. The description could have added more detail on what each depth costs or how to phrase the question, but the schema already covers the parameters well.

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 ('research'), a resource ('Pipeworx's 1517 STRUCTURED data sources'), and the key differentiator ('this is NOT open-web search'). It clearly distinguishes itself from ask_pipeworx and other siblings, and gives concrete examples of when to use it ('compare X and Y's regulatory + financial exposure').

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 explicitly says when to use this tool vs alternatives: 'If you are not signed in, use ask_pipeworx instead', 'For a single lookup use ask_pipeworx', and 'For BREAKING or colloquial CURRENT-NEWS ... prefer ask_pipeworx'. It also provides the account/plan gate and what depth levels do, giving clear selection criteria.

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