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

Even with readOnlyHint, openWorldHint, idempotentHint, and destructiveHint already annotated, the description adds substantial behavioral context: account requirement, paid tier for thorough depth, parallel routing to 5,798 tools, explicit gaps[] with "never invented," contradictions[] output, citation fetchability guarantees, semantic excerpting, and latency expectations. It goes well beyond what 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 description is long but every sentence earns its place: authentication, fallback tool, core behavior, use-case fit, exclusions, depth semantics, citation guarantees, and timing. It is front-loaded with the account requirement and fallback, then proceeds logically from core behavior to operational details. No redundant filler.

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 the absence of an output schema, the description is remarkably complete: it describes the findings packet structure, gaps and contradictions behavior, citation resolvability, hop semantics, and expected latency. An agent has enough context to decide whether to invoke it and to set expectations for the response.

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 baseline is 3; the description adds practical meaning beyond the schema by explaining that thorough requires a paid plan, that standard/thorough include contradiction scans, and that depth controls hop iteration and latency. It reinforces and enriches the schema's parameter descriptions without replacing them.

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-resource pair: "Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources ... in ONE call." It distinguishes itself from open-web search and from ask_pipeworx, while the sibling list shows no overlapping research tool with equivalent scope. The purpose is unmistakable.

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?

The description gives explicit when-to-use and when-not-to-use guidance: "Best for broad/multi-part questions over structured data," and "For a single lookup use ask_pipeworx," plus a category exclusion for breaking/current news. It also names the exact alternative tool if the user is not signed in, which directly steers tool selection.

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