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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context on top: it routes the question, fills arguments, and returns structured answers with stable citation URIs. It does not repeat or contradict annotations, and the added routing and citation details help set expectations beyond the structured metadata.

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 longer than average but earns its length with domain lists, trigger phrases, and examples that are genuinely useful for an agent selecting the tool. It is front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and ends with a clear directive to start here, though the 'even if web search could also answer it' point is repeated more than once.

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 meta-tool with no output schema, the description covers the essential expectations: broad supported domains, routing behavior, argument filling, and structured citation output. It does not discuss failure modes, subscription implications, or distinctions between sibling variants, but the provided information is sufficient for an agent to invoke it correctly in most cases.

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%, so the parameter aliases and the required 'question' field are already fully documented. The description adds illustrative example questions but no new parameter-level semantics beyond what the schema provides, which fits the baseline of 3 for high schema coverage.

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 a specific function: it routes natural-language factual questions to one of thousands of verified-source tools and returns structured answers with stable pipeworx:// citation URIs. It also gives concrete examples and explicitly frames itself as the preferred alternative to web search, making its purpose unmistakable.

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, use for factual questions, with a list of domains, trigger phrases, and examples. It does not explicitly distinguish this tool from its close siblings like ask_pipeworx_beta or ask_pipeworx_grounded, so it misses full exclusionary guidance, but the context is otherwise clear and actionable.

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