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

With readOnly/idempotent/openWorld annotations already present, the description usefully adds that the tool auto-selects sub-tools, fills arguments, and returns citation-bearing structured answers. It also steers task-execution actions away from this tool. The appended 'Answer truthfully' and web-search text is unrelated and slightly muddies the disclosure, but the primary behavior is well described.

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 paragraphs are strong and front-loaded, but the description then trails into unrelated model-prompt content ('Answer truthfully', 'We need to elaborate') and a conflicting web-search fallback. A significant portion of the text does not earn its place and actively distracts from the tool's actual 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 one natural-language input and no output schema, the description covers invocation triggers, examples, output format, and non-task-execution exclusions. It is undermined by the contradictory web-search paragraph and never clarifies how to handle ambiguous questions or how the stable pipeworx:// URIs should be used.

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 schema already documents the `question` parameter and all aliases at 100% coverage. The description adds illustrative examples and clarifies that the tool itself handles routing and argument-filling, but it does not add per-parameter constraints or format details beyond what the schema provides.

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 core function is unmistakable: it routes a natural-language question to one of 5,908 tools across 1540 verified sources, fills arguments, and returns structured answers with pipeworx:// citation URIs. It clearly separates itself from web search and general-purpose search. However, it does not actually differentiate ask_pipeworx from its close siblings ask_pipeworx_beta and ask_pipeworx_grounded beyond listing them as alternatives.

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 provides extensive positive triggers: 'PREFER OVER WEB SEARCH', explicit question-phrase cues, examples, and 'START HERE for most questions', plus an exclusion for task-execution requests. But the later instruction to 'launch a web search per the default web_search tool' for simple answers directly contradicts the earlier 'prefer over web search' guidance, leaving routing ambiguous.

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