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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds useful behavioral context: it routes to the right tool, fills arguments, returns structured answers with stable citation URIs, and is a single fast call on every tier. No contradiction with annotations.

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 long but front-loaded with the core 'prefer over web search' and routing decisions. The examples are helpful, though some repetitive trigger lists and marketing-style phrasing could be trimmed 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?

There is no output schema, but the description compensates by explaining the return format, citation URIs, and coverage of sources. It also addresses cost/latency expectations and alternatives. It doesn't cover failure or edge-case behavior, but it is sufficient for a default entry-point tool.

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 eight parameters are aliases for the same natural-language question field. The description adds no new parameter semantics beyond what the schema already documents, so 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?

Description states this is a general factual question-answering tool that routes to 6,404 tools and returns structured answers with pipeworx:// citation URIs. It explicitly distinguishes itself from ask_pipeworx_grounded and deep_research, making its role clear among siblings.

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?

Gives explicit guidance: 'PREFER OVER WEB SEARCH', 'START HERE', and 'Use whenever' with trigger phrases. It also explains when to step up to alternatives: ask_pipeworx_grounded for hallucination-resistant answers and deep_research for broad/multi-part questions.

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