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

The annotations already cover read-only/open-world/idempotent/non-destructive behavior, and the description adds substantial context: account and paid-tier requirements, structured-source scope, findings packet fields, gaps[] for unanswered facets, and an explicit 'never invented' no-hallucination guarantee. This goes well beyond what the annotations alone convey.

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 unique content is tight and front-loaded, but the description then repeats the same block dozens of times with progressive corruption and typos. This is not appropriately sized, most sentences do not earn their place, and the bloat severely harms readability.

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?

Despite the duplication, the first block covers purpose, auth fallback, best-use case, and return packet contents, which compensates for the absence of an output schema. Minor gaps remain: no latency expectations and no depth-selection guidance beyond what the schema already provides. Overall it is complete enough for selection and invocation.

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 applies; the schema fully documents question and depth, including enum semantics. The description only adds the account/pricing note for thorough, which the schema already states. No meaningful parameter meaning is added 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 first paragraph clearly states a specific function: grounded multi-source research over Pipeworx's 1506 structured data sources in one call, decomposing questions into facets and routing to tools in parallel. It also distinguishes itself from open-web search and from the single-lookup sibling ask_pipeworx. The purpose remains clear despite the repetitive text that follows.

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 explicitly tells the agent to use ask_pipeworx when not signed in and for single lookups, and says deep_research is best for broad/multi-part structured-data questions. It also frames the tool as NOT open-web search, which communicates when it does not apply. This is direct and actionable selection guidance.

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