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

Annotations already mark the tool read-only, open-world, idempotent, and non-destructive. The description adds substantial behavioral context beyond annotations: it requires an account, works only on structured data (not open-web), decomposes into facets, routes to 5,798 tools in parallel, returns a findings packet with citations and gaps, never invents answers, handles multi-step questions via iterative depth modes, includes contradictions for standard/thorough, and lists expected latency. No contradiction with annotations.

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 every sentence carries substantive information about behavior, alternatives, constraints, and output semantics. It is front-loaded with the account requirement and the most important routing distinction (ask_pipeworx if not signed in). It could be slightly tightened, but it earns its length given the tool's complexity and the absence of an output schema.

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?

Given the tool's complexity and lack of an output schema, the description is remarkably complete: it covers authentication, pricing tiers, supported data sources, what the tool does internally, what the return packet includes, what gaps and contradictions mean, citation resolvability, semantic excerpting behavior, and expected latency. An agent has enough context to decide when to invoke it and what to expect in return.

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 description coverage is 100%, so the baseline is 3, but the description goes well beyond the schema. It elaborates the depth enum's behavioral implications (quick=single hop, standard=gap-recovery hop + contradictions, thorough=iterative lead-chasing + gaps + contradictions) and explains that the question parameter accepts natural-language, broad, multi-part queries. This adds real operational guidance not present in the schema.

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: multi-source structured research across Pipeworx's 1517 structured data sources, decomposing questions and routing them to tools in parallel. It clearly distinguishes itself from open-web search and names the sibling ask_pipeworx as the alternative for single lookups, so an agent can tell them apart.

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?

Gives explicit when-to-use and when-not-to-use guidance: use ask_pipeworx if not signed in, use ask_pipeworx for single lookups, and use deep_research for broad/multi-part structured-data questions. It also notes that depth:'thorough' requires a paid plan, which is a key condition for selecting this tool over free alternatives.

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