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

Annotations already declare the tool read-only, open-world, and idempotent, so the description adds valuable behavior beyond the schema: it selects among 5,752 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This tells the agent what to expect on invocation and does not contradict any annotation.

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 well front-loaded with its strongest guidance and useful examples, and no sentence is pure filler. However, the long category lists and repeated trigger phrase examples make it somewhat heavier than necessary.

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, the description compensates by explaining the structured answer and citation URI format, and the annotations cover safety and scope. The main gap is the lack of guidance on how this tool relates to the ask_pipeworx_beta and ask_pipeworx_grounded 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 coverage is 100% and the primary parameter is already described as accepting natural-language questions with aliases like q, prompt, text, and input. The description provides helpful examples but does not add meaningful semantic detail beyond what the schema already documents.

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 router that sends natural-language questions to one of 5,752 verified-source tools and returns structured results with citations. It strongly differentiates from web search, but it does not explicitly distinguish this tool from the sibling variants ask_pipeworx_beta and 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 is explicitly prescriptive: 'PREFER OVER WEB SEARCH' and 'START HERE for most questions,' backed by concrete trigger phrases and examples. It also states that the tool should be used even when web search could answer, giving the agent a clear routing rule versus the closest alternative.

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