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

No annotations are provided, and the description itself is opaque. It does not state whether the tool is read-only, whether it performs network calls, or what 'connection methods' means. The claim that task text is discarded is not elaborated, and the side effects (if any) are completely undisclosed.

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, but it is poorly structured and filled with non-sequiturs (e.g., 'zone' as IANA timezone name in a tool about gateways). The brevity does not aid clarity; it creates confusion about the tool's actual function.

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 annotations, and a description that fails to explain the relationship between parameters and purpose, the tool is not adequately specified. An agent cannot determine what the tool returns or how to interpret the result, making it unusable without external knowledge.

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?

While every parameter has a schema description (e.g., 'Git ref name; discarded after the shape check'), these descriptions are generic and do not connect to the tool's stated purpose of finding a pay-per-call gateway. The meaning of each parameter in the context of this tool is unclear, and the descriptions do not compensate for the lack of coherence.

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 verb ('Find') and a resource ('public pay-per-call tool gateway'), but the rest is vague and contradictory: the parameters (ref, url, city, feed, host, json, path, zone, query) are unrelated to that purpose, and the phrase 'Task text discarded' is unexplained. It does not clearly differentiate from the many sibling tools that handle specific tasks (e.g., weather-hint, search-query-len).

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?

There is no guidance on when to use this tool versus any of the 27 siblings. No conditions, examples, or exclusions are provided, leaving the agent to guess when this tool is appropriate.

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