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

The description adds a wealth of behavioral context beyond what the annotations (readOnlyHint, openWorldHint, idempotentHint) provide: parallel facet decomposition, explicit gaps[] with a 'never invented' guarantee, gap-recovery hops per depth, contradictions[] scanning, semantic excerpting of large records ('not head-truncated'), resolvable citation_uri semantics, latency expectations (15-60s, up to ~90s for thorough), and auth/tier gating. No contradiction with annotations — 'never invented' and grounded sourcing are consistent with readOnlyHint=true.

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?

Every sentence earns its place — there is no filler — and the critical routing information (account required, use ask_pipeworx if not signed in, not open-web search) is front-loaded. However, the prose is structurally sprawling: heavily parenthetical run-ons and em-dash chains (the opening sentence alone packs three distinct facts) make the details harder to parse than necessary. The length is justified for a tool this complex, but tighter formatting would improve scannability.

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 carries the burden of explaining return values, and it does so thoroughly: the findings packet shape (verbatim evidence + confidence + source + fetched_at + pipeworx:// citation), the hop field and citation_uri guarantee, gaps[] and contradictions[] behavior, and the semantic-excerpting behavior for large records. It also covers latency, auth tiers, and what the tool is not. Only minor omissions exist (rate limits, exact unauthenticated error behavior), but for a tool of this complexity the coverage is exceptional.

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 with the schema doing the heavy lifting. The description goes beyond the schema by enriching the depth parameter with behavioral meaning: what each level actually does (gap recovery, chasing leads from the first pass), the paid gating for thorough, and the latency implications. It also clarifies what kinds of questions the question parameter is suited for ('Broad/multi-part is fine'). This is genuine added value, not schema repetition.

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 and resource: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources... in ONE call.' It explains the mechanism (decomposes into facets, routes in parallel to 5,798 tools) and explicitly differentiates itself from siblings: 'this is NOT open-web search' and 'For a single lookup use ask_pipeworx.' An agent can clearly tell this apart from ask_pipeworx and the other research-related siblings without opening schemas.

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 and when-not-to-use guidance with named alternatives: use when signed in and dealing with 'broad/multi-part questions over structured data' with concrete examples ('compare X and Y's regulatory + financial exposure'); use ask_pipeworx for single lookups and for unauthenticated users ('If you are not signed in, use ask_pipeworx instead — it works on every tier'). This is textbook routing guidance — nothing is left to inference.

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