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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds meaningful context beyond that: it is an auto-routing tool that fills arguments, uses verified sources, and returns citation URIs. It does not discuss failure modes or limits, but the safety profile is covered by annotations and the routing/citation behavior is a useful disclosure.

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 the most important instruction and includes useful examples and sibling routing. However, it becomes a long run-on passage with grammar issues, repeated ideas, and confusing fragments such as 'for an answer spanning many entities with cutoffs and recency aware, use bet_research for maneuver-weighted scenarios.' Some sentences, like 'There is also the beta variant ask_pipeworx_beta', add little structural 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?

For a router tool with one required natural-language parameter and no output schema, the description covers the core contract: when to use it, what it does internally, what it returns, and how it compares to major siblings. It is largely complete, but the confusing alternative-routing sentences and lack of any mention of response format details beyond 'structured answer with citation URIs' keep it from being fully complete.

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 baseline is 3. All six parameters are aliases for 'question' and are described as such in the schema, and the description plus schema examples make clear that a natural-language question is expected. There is no additional depth about input formatting, length, or language constraints, but the schema already carries the necessary semantic weight.

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 states a specific core function: it routes questions to one of 5,798 tools across 1,517 verified sources, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. This clearly distinguishes the tool from generic web search and from sibling research tools like deep_research or validate_claim.

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 tool over web search for factual/current-data questions, lists many covered domains, gives trigger phrases, and names alternatives such as ask_pipeworx_grounded, deep_research, validate_claim, and compare_entities. However, the routing guidance is muddled by typos and confusing references like 'single:ask_pipeworx' and 'Use for single-answer funnel: deep_research', which reduce its reliability.

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