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

While annotations already set readOnly, openWorld, idempotent, and destructive hints, the description adds substantial behavioral context: account/plan requirements, parallel decomposition across 5,724 tools, a findings packet with verbatim evidence + confidence + source + fetched_at, gaps[] that are never invented, contradiction[] scans for certain depths, latency expectations, semantic excerpting, and resolvable pipeworx:// citations. This far exceeds what annotations could convey.

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, but the tool is complex and nearly every sentence carries operational information rather than filler. It front-loads the critical account prerequisite before the value proposition, then proceeds logically from what it does to when to use it to behavioral details. A little restructuring into paragraphs or bullets would help, but it earns its length.

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?

With no output schema, the description fully compensates by explaining the return shape: findings packet, verbatim evidence, confidence, source, fetched_at, citation_uri, hop, gaps[], and contradictions[]. It also covers prerequisites, latency, source scope, and failure modes. An agent has everything needed to decide whether to call this tool and what to expect back.

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 extra meaning by explaining that depth:'thorough' requires a paid plan and clarifying what each depth level does behaviorally (gap recovery, lead-chasing, contradictions scan). question is also enriched by noting that broad/multi-part input is acceptable. This is more than the schema alone provides, earning a 4.

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 names a specific verb and resource: grounded multi-source research over Pipeworx's 1,497 structured data sources in a single call. It explicitly distinguishes itself from open-web search and from ask_pipeworx, and even says what it is NOT — making sibling differentiation clear. This is well beyond a generic 'performs research' statement.

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 guidance: broad/multi-part structured-data questions like 'compare X and Y's regulatory + financial exposure'. It also names alternatives and conditions — use ask_pipeworx for a single lookup, and prefer it for breaking or colloquial current-news topics. The account-requirement fallback ('if not signed in, use ask_pipeworx') further clarifies selection.

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