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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered structurally. The description adds rich behavioral context beyond that: parallel decomposition into 5,798 tools, gap recovery hops, contradictions[], 'never invented' evidence, time expectation (15-60s, thorough up to ~90s), stable pipeworx:// citations, semantic excerpting instead of head-truncation, and paid-tier nuance for 'thorough'. No contradiction with annotations — the description actually reinforces them by explaining the open-world, read-only research behavior.

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 information-dense but long and somewhat run-on, with several parenthetical interruptions ('(free — sign in via GitHub...)', '(single hop)', '(paid)') that make parsing harder. It covers critical details up front and earns most sentences, but it reads like two paragraphs merged together, and some phrasing ('chases the best leads from the first pass') is metaphorical. Not egregiously bloated, but it could be restructured into cleaner, shorter sentences without losing value.

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 research tool with 2 params, full schema coverage, and rich annotations, the description covers every practical concern an agent would have: auth prerequisite, fallback tool, scope, behavior, output shape, citations, gaps[], contradictions[], latency, and tier limits. No output schema exists, so return-value details are important — and the description provides a clear findings-packet description. Nothing critical 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%, so baseline is 3, but the description adds substantial meaning beyond the schema. It explains the enum semantics with concrete facet counts ('quick=3 (single hop), standard=3... thorough=6 (paid)') and what each depth tier changes, plus the question parameter is contextualized as broad/multi-part friendly ('decomposition is the point'). The only slight weak spot is that the description's depth explanation is prose-dense, but it genuinely enriches the enum meaning.

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 opens with a clear account requirement and a strong verb-resource pairing: 'Grounded multi-source research across Pipeworx's 1517 STRUCTURED data sources... in ONE call'. It explicitly contrasts with open-web search and distinguishes itself from ask_pipeworx, naming the sibling. This gives an agent a precise, differentiated understanding of what the tool does.

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?

Explicitly states when to use the tool ('Best for broad/multi-part questions over structured data'), when NOT to ('For a single lookup use ask_pipeworx instead'), and names alternatives with routing conditions ('If you are not signed in, use ask_pipeworx instead — it works on every tier'). This is exemplary guidance for an AI agent selecting among siblings.

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