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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), the description adds substantial behavioral disclosure: account/payment requirements, parallelism across 5,743 tools, explicit gaps[] for unanswered facets, contradictions[] returns, semantic excerpting rather than head-truncation, stable citations that are always fetchable, and expected latency ranges. This richly clarifies what happens during execution.

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 nearly every sentence carries load-bearing guidance: account constraints, usage routing, output shape, gap handling, depth semantics, citation behavior, latency. It is front-loaded with the account requirement and the alternative-tool fallback. It loses one point for density: the parenthetical-heavy, run-on style can make it harder to parse in one pass.

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 tool with no output schema, the description is exceptionally complete. It explains the findings packet structure (verbatim evidence + confidence + source + fetched_at + pipeworx:// citation), the behavior of gaps[] (never invented), contradictions[], hop field, citation_uri fetchability, excerpting behavior, timing, and prerequisites. An agent has everything needed to invoke correctly and interpret results.

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 baseline is 3. The description adds value beyond the raw schema by explaining the practical difference between depth options: 'quick=3 (single hop)', 'standard=3 (default; adds a gap-recovery hop ... plus a contradictions[] scan)', and 'thorough=6 (paid; adds a full iterative hop ...)'. It also explains that 'question' can be broad/multi-part. Slight deduction because the description doesn't add new information about the question parameter format beyond schema's natural-language note, but the depth elaboration is genuinely useful.

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+resource: 'Grounded multi-source research across Pipeworx's 1500 STRUCTURED data sources ... in ONE call', and explicitly distinguishes itself from open-web search. It also differentiates from ask_pipeworx by positioning itself for broad/multi-part questions. An agent can clearly identify what this tool does and how it differs from 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?

The description gives explicit when-to-use/when-not-to-use guidance: use ask_pipeworx for single lookups, breaking/colloquial current-news topics, or when not signed in. It also details depth-level semantics and the second-hop iteration behavior, so the agent knows exactly which depth to pick and when the tool is appropriate.

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