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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses account requirements, the paid tier for thorough, parallel decomposition across 5,798 tools, output packet contents, gaps[] behavior, contradictions[], citation URI resolvability, semantic excerpting, and latency expectations. It is exceptionally transparent about how the tool behaves.

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-loaded with the most decision-relevant details: account requirements, core function, alternatives, then output mechanics and latency. It earns its length, though it slightly repeats depth/enum details already present in the 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?

With no output schema present, the description fully covers what the agent will receive: per-finding evidence, confidence, source, fetched_at, hop, citation_uri, gaps, contradictions, and semantic excerpts. It also covers prerequisites, restrictions, timing, and expected scope, making the tool callable without further documentation.

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% and the schema already documents question and depth in detail. The description adds meaningful examples of suitable questions and reinforces the boundary between single and multi-part queries, so it goes slightly beyond a baseline but does not dramatically extend 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 concrete, specific action: grounded multi-source research across Pipeworx's 1,517 structured data sources in one call, explicitly contrasted with open-web search. It clearly distinguishes deep_research from siblings by positioning it against ask_pipeworx for single lookups.

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?

It gives explicit routing rules: use deep_research for broad/multi-part questions over structured data, use ask_pipeworx for single lookups, and use ask_pipeworx when not signed in. This is directly actionable for an agent deciding between tools.

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