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

With no annotations, the description carries the burden; it does disclose some behaviors: it 'Returns connection methods', discards task text, and parameter notes say 'no disk access' and 'discarded after the check'. However, it does not explain what 'connection methods' are, whether calls cost money, or what side effects occur.

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 mostly front-loaded, but the contradictory 'Task text discarded' sentence undermines the structure. It is concise but not clearly organized.

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 tool with no output schema and no annotations, the description leaves key context missing: the required task input (if any), the format of the returned connection methods, pricing implications, and the relationship to sibling tools. It cannot be used confidently.

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?

Every parameter has a description (100% coverage), so the baseline is 3, but the descriptions are incoherent in context: they describe discarded inputs, unrelated concepts (Git refs, RSS titles, timezones), and 'normalize or cite' alternatives. They do not explain how any parameter maps to the tool's stated purpose of finding a gateway.

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 and object ('Find a public pay-per-call tool gateway') and lists example tasks, but the phrase 'Task text discarded' contradicts the stated purpose and the input schema has no task parameter. It is unclear what 'public pay-per-call tool gateway' means or how the tool actually selects a gateway.

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 gives example use cases ('weather, search, scrape, or voice') but no explicit when-to-use guidance, no alternatives, and no warning that task text is discarded. It does not say how this differs from sibling tools like weather-hint, web-fetch, or normalize-url.

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