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

The description goes far beyond the readOnly/openWorld/idempotent annotations by disclosing the findings packet fields, gaps[] behavior, non-hallucination guarantee, fetchable citation_uri conditions, contradictions[] for standard/thorough, semantic excerpting of large records, and expected latency. No annotation contradicts the described behavior.

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 dense and front-loads the critical account gate before the purpose. Almost every sentence carries useful operational information, though the routing guidance to ask_pipeworx appears more than once and there is a minor apparent text artifact, preventing a perfect conciseness score.

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 documenting return packet contents, citations, gaps, contradictions, quoting behavior, latency, and account/tier requirements. An agent has enough context to invoke the tool, set expectations around time, and understand what the result will contain.

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?

Even though the schema covers 100% of parameters, the description adds meaning: concrete example prompts, confirmation that broad/multi-part questions are acceptable, and a clearer explanation of depth's paid gate and the hop/contradiction behavior beyond the enum descriptions. This materially helps an agent choose question phrasing and depth.

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 function: grounded multi-source research across Pipeworx's 1517 structured data sources, decomposing questions into facets and routing them to tools in parallel. It explicitly contrasts itself with open-web search and with ask_pipeworx for single lookups, so an agent can distinguish it from 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?

Usage criteria are explicit: use for broad/multi-part questions over structured data; use ask_pipeworx instead for a single lookup; use ask_pipeworx if not signed in because it works on every tier; thorough requires a paid plan. This gives both positive and negative routing guidance.

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