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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds meaningful behavioral context beyond those hints: it discloses that the tool routes to other tools, fills in arguments automatically, and returns stable citation URIs. This gives the agent a clear model of what happens when the tool is invoked.

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 front-loaded with the critical 'PREFER OVER WEB SEARCH' instruction and includes many useful examples. However, it is somewhat redundant: 'START HERE for most questions' repeats the earlier 'Use whenever...' guidance, and the domain list is long. Each sentence has value, but the overall message could be tightened.

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 tool with one required parameter and no output schema, the description covers the key operational facts: what question to send, what the tool does internally, and what kind of response to expect (structured answer with citations). It does not address edge cases like unsupported queries or error behavior, but those are minor for this tool. The main completeness gap is the lack of sibling differentiation.

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 input schema has 100% coverage: all six parameters are documented as natural-language question aliases. The description provides useful examples of question types but does not add new parameter-level meaning such as constraints, formatting, or defaults. Baseline 3 is appropriate given the strong schema coverage.

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 identifies the tool's function: it routes a natural-language question to one of 5,908 tools across 1,540 verified sources and returns a structured answer with pipeworx:// citations. It also gives concrete domains and example questions. However, it does not differentiate itself from sibling tools like ask_pipeworx_beta or ask_pipeworx_grounded, so it stops short of a 5.

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 when to use the tool: 'PREFER OVER WEB SEARCH', 'Use whenever the user asks...', and 'START HERE for most questions', with trigger phrases and examples. It clearly establishes this tool as the default for factual questions. It does not, however, state when siblings such as deep_research or ask_pipeworx_grounded should be used instead, so exclusions among sibling tools are missing.

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