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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description usefully supplements this by explaining that the tool routes to many sources, fills arguments, and returns structured answers with stable citation URIs, which adds behavioral context beyond the annotations. 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 long but well-structured and front-loaded with the most important directive: PREFER OVER WEB SEARCH. The domain lists and examples are informative rather than redundant, though some trimming of the enumerated source categories could make it tighter 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?

Given there is no output schema, the description adequately covers the return contract by mentioning the structured answer and stable pipeworx:// citation URIs. It also gives broad domain coverage, query phrasing patterns, concrete examples, and routing behavior, so an agent has enough context to select and invoke 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?

Schema description coverage is 100%, so the input schema already fully documents the required 'question' parameter and its five aliases. The description adds natural-language usage examples and general guidance but does not need to explain parameter semantics further. Baseline 3 is appropriate because the schema carries the parameter burden.

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 that ask_pipeworx routes questions to 5,801 tools across 1,517 verified sources and returns structured answers with pipeworx:// citations, giving a specific verb, resource, and scope. However, it does not distinguish itself from the sibling ask_pipeworx_beta or ask_pipeworx_grounded tools, so it stops short of full sibling differentiation.

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 is explicit about preferring this tool over web search, lists concrete query patterns such as 'what is', 'look up', 'find', and 'get the latest', and provides multiple examples. It does not, however, state explicit exclusions or explain when sibling ask_pipeworx variants should be used instead, so the guidance is clear context without complete when-not coverage.

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