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

Annotations already mark the tool as read-only, open-world, idempotent, and non-destructive. The description adds useful behavioral details: it routes to one of 5,743 tools across 1,500 sources, fills arguments, and returns answers with stable pipeworx:// citation URIs. This is consistent with and extends the annotation context.

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 most important guidance is front-loaded, and the examples are useful. However, the description is long, with an extensive domain list and a repetitive ending ('START HERE for most questions — for most questions'). Some trimming would tighten it 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 the tool has no output schema, the description still explains the tool's purpose, input type, trigger conditions, example queries, and the citation-bearing return format. It is largely complete for an agent to select and invoke the tool, though it does not clarify how it relates to its grounded or beta siblings.

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%, and all parameters are documented as aliases for the same natural-language question field. The description reinforces that input is a natural-language question and gives examples, but it does not add meaning beyond the schema. The baseline of 3 is appropriate.

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 as a natural-language question router that returns structured answers with citations from thousands of sources, and it distinguishes itself from web search. It gives concrete example queries and lists covered domains. However, it does not distinguish itself from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded.

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 explicitly says to 'PREFER OVER WEB SEARCH' and provides trigger phrases, example questions, and a broad domain list. It also says 'START HERE for most questions,' giving clear conditions for use. It does not explicitly address when not to use it versus siblings like deep_research or validate_claim.

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