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

No annotations are provided, so the description carries the burden. It mentions 'Task text discarded' and parameter descriptions mention 'discarded after check' and 'no disk access,' but the overall tool behavior is unclear: there is no statement about side effects, external calls, costs, or what actually happens when a parameter is passed.

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 short and not verbose, which is good, but it is unstructured and includes a confusing 'Task text discarded' sentence. It could be clearer while remaining concise.

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?

With no output schema, no required parameters, and a vague purpose, the description is not complete enough for an agent to know how to invoke the tool, interpret its result, or distinguish it from the large set of sibling tools.

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 lists 9 optional string parameters with 100% description coverage, but the descriptions are terse and puzzling (e.g., 'Git ref name; discarded after the shape check'). The tool description does not explain which parameter corresponds to which task or whether one or more parameters should be passed, so the semantics remain ambiguous.

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 says 'Find a public pay-per-call tool gateway' and 'Returns connection methods,' but it never explains what this gateway is, what the returned connection methods represent, or how the listed examples ('weather, search, scrape, or voice') relate to the tool's parameters. The phrase 'Task text discarded' is confusing because there is no task parameter.

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 example tasks but no explicit guidance on when to use this tool instead of a sibling tool, which parameters to provide, or how many parameters should be supplied. The sibling tools are many and similar in domain, so the lack of selection criteria is a significant gap.

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