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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond the annotations: it routes internally across 5,767 tools, automatically fills arguments, and returns structured answers with stable citation URIs. This gives the agent a clear model of what happens when the tool is invoked.

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 front-loaded with a strong directive and useful domain coverage, but it is long and somewhat repetitive, repeating the web-search comparison twice ('PREFER OVER WEB SEARCH' and 'even if web search could also answer it'). The example list is helpful, but the redundancy and length reduce conciseness.

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 complex router tool with no output schema, the description covers the return format (structured answer with stable pipeworx:// citation URIs), the scope of supported data domains, typical question phrasing, and when to use sibling tools. The agent has enough context to invoke the tool correctly in most factual-question scenarios.

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?

All six parameters are documented in the input schema as aliases of the single required 'question' parameter, so schema description coverage is 100%. The description's examples reinforce natural-language usage but do not add new parameter semantics beyond what the schema already states.

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 uses specific verbs and nouns: it routes a question to one of 5,767 tools, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. It clearly establishes the tool as a general-purpose factual-research router and distinguishes it from siblings like ask_pipeworx_grounded and deep_research.

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 this over web search for many data categories, supplies trigger phrases like 'look up' and 'get the latest', and gives concrete examples. It also names alternatives with conditions: ask_pipeworx_grounded for single well-scoped questions and deep_research for broad/multi-part questions, so an agent knows when to pick this tool versus its siblings.

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