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

Beyond the annotations, the description discloses important behavioral traits: the tool routes to a large corpus of verified sources, fills arguments automatically, and returns structured answers with stable citation URIs. This tells the agent what happens during invocation and what kind of output to expect. It does not discuss failure modes, but annotations already cover read-only, idempotent, open-world behavior.

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 beginning is strong and front-loaded, but the description degenerates into a long block of repeated 'START HERE for most questions' phrases. This is severe redundancy and does not meet the standard that every sentence should earn its place. The tail appears to be corrupted or accidentally repeated text.

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 input type, provides varied examples, states the domains it handles, and explains that the output is a structured answer with pipeworx:// citation URIs. It is sufficient for an agent to decide when and how to invoke it, though a richer return-format description would improve 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?

The schema covers 100% of parameters and documents that question, q, text, input, query, and prompt are all aliases for the same natural-language request. The description adds no additional parameter-level semantics beyond what the schema already provides. The examples are useful but do not raise the score above the baseline.

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 what the tool does: it routes a question to the right one of 5,908 tools, fills arguments, and returns a structured answer with pipeworx:// citation URIs. This is a specific verb and resource, and it clearly positions the tool as a factual-data orchestration tool. However, it does not explicitly distinguish itself from sibling tools 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 gives explicit when-to-use guidance: 'PREFER OVER WEB SEARCH' and 'Use whenever the user asks...' followed by a broad list of query types and concrete examples. It even states to use it 'even if web search could also answer it,' and it names web search as the alternative. This is strong, actionable routing guidance.

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