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

The annotations already mark it read-only, idempotent, and non-destructive. The description goes further by explaining decomposition into facets, parallel routing, the findings packet shape, explicit gaps[], contradictions[] for standard/thorough, semantic excerpting, citation fetchability, and expected latency. No contradiction with annotations exists.

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 with no filler, but it is long and packs many details into sprawling clauses. The most important routing and auth constraints are near the front, yet behavioral details like contradictions, excerpting, and latency arrive later in a somewhat run-on structure. Still, every sentence contributes meaningful content.

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?

With no output schema provided, the description carefully covers what the agent will receive: verbatim evidence, confidence, source, fetched_at, stable pipeworx:// citations, gaps[], and contradictions[]. It also covers auth requirements, depth-tier access, latency, and alternatives. Nothing critical is missing for selecting or invoking the tool correctly.

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?

The schema already documents both parameters at 100% coverage, including detailed depth enum semantics. The description adds extra value by clarifying that the 'question' parameter is meant for broad/multi-part questions and that single lookups belong elsewhere. It also enriches the behavioral meaning of the depth tiers, so it adds more than the baseline.

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'. It also explicitly distinguishes itself from open-web search and from ask_pipeworx, making its scope immediately identifiable.

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 usage context: it is 'Best for broad/multi-part questions over structured data', and when not to use it: 'For a single lookup use ask_pipeworx instead' and 'If you are not signed in, use ask_pipeworx'. It also warns about the paid tier for thorough depth. This is strong, explicit routing guidance.

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