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

Despite annotations already covering read-only/idempotent behavior, the description adds substantial operational detail: parallel routing across 5,767 tools, findings packet contents, gaps[] for unanswered facets, no invented evidence, latency expectations, contradiction scanning, and semantic excerpting. This goes well beyond what annotations or schema provide.

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 dense and useful at first, but it becomes bloated and structurally broken near the end with a garbled tail like 'LLM, not many). For a single lookup use ask_pipeworx instead.' Not every sentence earns its place, and the duplicate alternative guidance undermines clarity.

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?

For a complex tool with no output schema, the description covers inputs, account/auth constraints, depth semantics, output shape, latency, citation behavior, and edge cases like gaps and contradictions. The only reason it is not a 5 is the incoherent trailing fragment that slightly reduces trust in the definition's overall quality.

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 schema already documents both parameters and the depth enum thoroughly. The description mostly restates that thorough is paid and that questions can be broad/multi-part, adding little parameter-specific meaning beyond 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 uses a specific verb and resource: 'Grounded multi-source research across Pipeworx's 1506 STRUCTURED data sources' in ONE call. It clearly distinguishes itself from open-web search and from the ask_pipeworx sibling for single lookups, leaving no doubt about its role.

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?

Explicit when-to-use guidance is present: 'Best for broad/multi-part questions over structured data' and 'For a single lookup use ask_pipeworx instead.' It also gives a concrete fallback for unsigned-in users, making the selection criteria actionable.

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