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

The description goes well beyond the annotations by covering auth requirements, latency expectations, the never-invent guarantee via explicit gaps[], contradictions[], hop fields, resolvable citation_uris, and semantic excerpting of large records. It does not contradict the readOnly/openWorld/idempotent 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 mostly earns its length given the tool's complexity. It front-loads the account requirement and sibling alternative, but the single-lookup routing is stated twice and the dense single-paragraph format makes it harder to scan.

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?

Even without an output schema, the description fully specifies the return packet: verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citation, gaps[], contradictions[], and hop field. It also explains timing, citation fetchability, and how deep-record content is excerpted, so an agent knows what to expect and how to 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?

The input schema already documents both parameters fully, including the depth enum's hop behavior, default, and paid tier. The description mostly reinforces this rather than adding new syntactic meaning, though it does provide a concrete example question and contextual notes on latency and gap recovery.

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 clearly identifies a specific verb and resource: grounded multi-source research across Pipeworx's 1517 structured data sources, decomposing questions into facets and routing them to 5,798 tools in parallel. It also distinguishes itself from open-web search and from sibling ask_pipeworx, so an agent can tell exactly what this tool does.

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 guidance is explicit: use deep_research for broad or multi-part structured-data questions, and use ask_pipeworx instead for single lookups or when not signed in. It also states the account requirement and paid plan needed for the thorough depth, leaving little ambiguity about when this tool is appropriate.

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