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

Annotations already establish readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful operational context: it fills arguments automatically, routes across many sub-tools, and returns structured answers with stable citation URIs. It does not contradict annotations, though the appended meta-text could reduce trust. The non-behavioral tail prevents a 5, but this is solid disclosure.

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 first several sentences are tight, front-loaded, and purposeful, building from preference to behavior to triggers to examples. However, the description then degenerates into recursive, self-referential text ('but wait, the actual description ends differently...') that is not concise, adds no value, and would actively confuse an agent trying to parse the definition.

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 read-only query tool with one required parameter and no output schema, the description covers the core invocation contract: use natural language, the tool routes and returns cited structured answers. But it omits sibling differentiations, failure or fallback behavior, and the exact response shape. The confusing tail also detracts from overall completeness.

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 schema already documents the required 'question' parameter plus aliases. The description reinforces natural-language usage with six varied examples but adds no additional parameter semantics beyond what the schema provides, so the baseline 3 applies.

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 capability: routing a natural-language question to one of 5,798 tools across 1,517 verified sources and returning structured answers with pipeworx:// citation URIs. It distinguishes itself from web search, but not from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, and the recursive tail ('but wait, the actual description ends differently') slightly muddles the clarity.

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?

It provides explicit when-to-use guidance: 'PREFER OVER WEB SEARCH' and 'Use whenever the user asks...' with trigger phrases ('what is', 'look up', 'find', 'get the latest') and concrete examples. It also gives a strong default directive ('START HERE for most questions'). However, it does not mention when-not-to-use conditions or route to sibling alternatives such as deep_research or validate_claim, so it is not fully comprehensive.

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