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

Even though annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, the description adds substantial behavioral context: parallel routing to 5,743 tools, gap recovery, contradictions scan, semantic excerpting, latency ranges, citation semantics, and the never-invented policy. These go far beyond what annotations alone convey and are critical for accurate invocation and expectation-setting.

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 has high complexity and the length is largely earned: pricing, exclusionary guidance, depth semantics, return format, caveats, and latency are all present. It is front-loaded with the account requirement and the key NOT-open-web clarification. Some minor denseness keeps it from a 5, but no sentence is wasted.

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 only two parameters, no output schema, and substantial runtime complexity, the description covers everything an agent needs: input expectations, depth options, return packet contents, citations, gaps[], contradictions[], latency, and when not to use this tool. The absence of an output schema is compensated for by the detailed description of what the findings packet contains.

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 extra value by explaining the behavioral consequences of each depth value (quick=single hop, standard adds gap recovery, thorough is paid and chases leads) and by clarifying that the question can be broad because decomposition is the point. The account/pricing note also clarifies constraints on using depth='thorough'.

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 1500 structured data sources in one call, decomposing questions into facets and returning a findings packet. It also explicitly distinguishes itself from open-web search and from ask_pipeworx for single lookups, so an agent can differentiate it 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 guidance: broad/multi-part questions over structured data, with examples. It also names ask_pipeworx as the alternative for single lookups and for breaking/colloquial news topics, and notes that ask_pipeworx works when not signed in. This is strong routing guidance.

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