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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, but the description goes well beyond them: account/tier gating, expected latency (15-60s, up to ~90s), parallel fan-out across 6,693 tools, gap recovery vs. lead-chasing per depth, contradiction scanning, and semantic excerpting instead of head truncation. The only minor gap is that return payload details are partly assumed rather than pinned down, but this is a genuinely rich behavioral disclosure.

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?

Front-loaded with the gating constraint (account/paid tier) that determines whether the tool is even usable, then the core function, then routing alternatives. It is dense rather than padded, though ask_pipeworx is referenced three separate times and the citation-resolvability point is stated twice, which slightly exceeds what the content needs.

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?

There is no output schema, so the description carries the return-value burden and does it: a findings packet with verbatim evidence, confidence, source, fetched_at, a stable pipeworx:// citation, gaps[], contradictions[], and a hop field. For a complex multi-hop research tool with 9 parameters, nothing an agent needs to call it correctly is missing.

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%, including per-alias descriptions and a full enum description for depth, so baseline 3 applies. The description restates the depth semantics already in the schema and adds only the tier gating for depth:'thorough', which is behavioral rather than parameter-level clarification.

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?

States a specific verb and resource — grounded multi-source research over Pipeworx's 1,761 structured data sources — and explicitly disambiguates the mode ('this is NOT open-web search'). An agent can distinguish it from siblings like ask_pipeworx or search without reading either 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?

Names alternatives and the exact conditions selecting them: use ask_pipeworx if unsigned or for a single lookup, and prefer ask_pipeworx for breaking/colloquial news because deep_research returns empty gaps[] there. It also states the 'best for' case (broad/multi-part structured-data questions), giving both when and when-not guidance.

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