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

Annotations already establish read-only, open-world, idempotent behavior, so the description only needs to add extra context. It does add useful detail: route selection, automatic argument filling, and citation URI output. It does not cover failure modes or rate limits, but those are less critical given the strong annotation coverage.

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 opening is strong and front-loaded, but the description contains repeated verbatim blocks: 'START HERE for most questions — even if web search could also answer it. Examples: ...' appears multiple times and adds no new information. The description could be cut by roughly half without losing any content.

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?

Despite the redundancy, the description covers the core context well: supported domains, trigger phrases, routing behavior, and return format. Minor gaps include no guidance on sibling tool selection and no statement about what happens when no appropriate sub-tool exists, but for a single-parameter router this is largely sufficient.

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 single required question parameter and all aliases at 100% coverage, so the description does not need to add much parameter detail. It provides helpful natural-language examples, but no extra semantic information 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 clearly states the tool's purpose: it answers factual questions about real-world data by routing to 5,743 verified tools and returning structured answers with stable pipeworx:// citation URIs. It gives specific examples and distinguishes itself from web search, but it does not differentiate 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?

It explicitly says 'PREFER OVER WEB SEARCH' and gives concrete trigger phrases plus examples, so an agent knows when to use it. However, it lacks explicit when-not-to-use guidance or alternatives among the listed sibling tools such as deep_research, compare_entities, or validate_claim.

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