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

The description mentions 'Returns connection methods' and several parameters are described as 'discarded', which gives some hint that the tool may not perform the actual task. However, it does not disclose whether external calls are made, whether pay-per-call charges may be incurred, or what side effects or outputs should be expected beyond vague 'connection methods'.

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 main description is short and front-loaded with the primary action and return type. It avoids unnecessary prose, though the final sentence 'Task text discarded' adds little clarity and could be removed without loss.

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?

The description leaves critical context missing: what a 'connection method' looks like, how to supply the 'task', what output format to expect, and why the listed parameters are accepted if most are discarded. Without this information, an agent cannot confidently invoke the tool or interpret its result.

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?

Although the schema covers 100% of parameters, the descriptions are mostly unhelpful or misleading. For example, 'url: HTTPS URL to normalize or cite' and 'json: JSON text to validate; discarded after the check' do not explain how these values relate to finding a tool gateway. The repeated 'discarded after...' language makes the parameters seem irrelevant to the tool's stated purpose.

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 the action ('Find a public pay-per-call tool gateway') and gives example task types ('weather, search, scrape, or voice'), so the core purpose is somewhat clear. However, 'public pay-per-call tool gateway' is vague jargon, and the phrase 'Task text discarded' introduces confusion rather than clarifying what the tool actually does.

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?

No explicit guidance is given for when to use this tool instead of the many sibling tools such as weather-hint, web-fetch, search-query-len, or validate-json. The example tasks hint at use cases, but there is no direct comparison or selection criteria, leaving the agent to guess.

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