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

Annotations (readOnly/openWorld/idempotent/non-destructive) carry the safety profile, and the description adds substantial context beyond them: GitHub sign-in requirement, paid gate for 'thorough', latency expectations (15-60s, up to ~90s), the groundedness guarantee ("explicit gaps[] ... never invented"), contradictions[] semantics per depth, semantic excerpting instead of head-truncation, and the fetchable-citation guarantee. readOnlyHint is consistent with a research tool.

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?

Dense but largely justified for a tool with three depth modes, an auth gate, and a rich output contract. It loses a point because depth-mode mechanics are explained both here and in the schema's enum descriptions, creating redundancy, and the opening sentence is overloaded with nested quoted terms.

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 the auth prerequisite, the sibling fallback, output packet contents (verbatim evidence + confidence + source + fetched_at + citation), gaps[] and contradictions[] behavior, depth semantics, question phrasing guidance with examples, and timing. Nothing an agent needs to decide whether to call it or to set expectations is missing.

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 depth enum description is already detailed, so the baseline is 3. The description adds value beyond the schema by tying depth to the paid plan, attaching latency expectations to each mode, and clarifying that 'standard' and 'thorough' both return contradictions[] — details the schema does not convey.

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?

States a specific verb and resource — "grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources" — and explicitly differentiates itself from alternatives ("this is NOT open-web search"). It also names the sibling it is not ("For a single lookup use ask_pipeworx"), so an agent can tell them apart immediately.

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?

Gives explicit when-to-use ("Best for broad/multi-part questions over structured data"), when-not-to-use ("For a single lookup use ask_pipeworx"), and an auth-gated fallback ("If you are not signed in, use ask_pipeworx instead — it works on every tier"). The routing guidance is concrete and leaves nothing to inference.

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