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

Even with readOnlyHint/openWorldHint/idempotentHint annotations, the description adds substantial behavioral context: parallel decomposition across tools, findings packet structure with evidence/confidence/source/citation, explicit gaps[] for unanswered facets, contradiction scanning for standard and thorough depths, semantic excerpting, and expected latency. No annotation is contradicted.

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 information-dense: every clause adds operational value, from auth requirements to output format to latency. It is front-loaded with the most important constraint (account required) and the alternative tool. Slight redundancy around the contradiction[-] scan and depth semantics keeps it from a 5.

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?

There is no output schema, so the description carries the full burden of explaining return behavior, and it does so thoroughly: findings packet contents, verbatim evidence, confidence, source, fetched_at, fetchable pipeworx:// citations, gaps[], contradictions[], excerpting behavior, latency, and account/tier constraints. An agent has enough context to decide when to call it and what to expect back.

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 already explains depth and question well, so the description does not need to re-document them. It adds meaningful parameter-level context beyond the schema by noting that 'thorough' requires a paid plan, attaching latency expectations to quick/standard/thorough, and clarifying that single-lookup questions should be routed to ask_pipeworx instead.

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 states a specific verb and resource: grounded multi-source research across Pipeworx's structured data sources in one call. It also differentiates itself from siblings by explicitly saying 'this is NOT open-web search' and by framing its best use case as broad/multi-part questions, with a direct pointer to 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?

The description gives explicit when-to-use and when-not-to-use guidance: use ask_pipeworx if not signed in, use ask_pipeworx for single lookups, and use deep_research for broad/multi-part structured-data questions. It also ties the 'thorough' depth level to a paid plan, preventing incorrect invocation.

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