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

With no annotations present, the description carries some behavioral burden. It does disclose that 'Task text discarded,' which is a meaningful privacy/disposal trait, and it says it returns connection methods. However, it does not describe other behavioral aspects like permission needs, rate limits, or side effects, and the step-by-step disposal is mostly left to the parameter schema.

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, front-loaded with the main purpose, and all three sentences add information. The line 'Task text discarded' is a little cryptic and not directly tied to any schema property, but overall the size and ordering are reasonable.

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?

Given nine optional parameters, no output schema, and no annotations, the description is not sufficient. It never explains what actually causes the tool to match one param or task to a gateway, how the provided parameters map to the tool selection, or what shape the returned connection methods take. The description would need substantially more detail to allow reliable invocation.

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 parameter descriptions already provide 100% coverage for the 9 optional properties, so the baseline is 3. The tool description itself adds no additional parameter-level meaning beyond the schema's 'discarded after...' notes and does not explain how the many disjoint parameters (ref, url, city, path, zone, etc.) should be combined or which ones are relevant to a task. It meets the baseline for schema coverage but adds no extra semantic clarity.

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 uses a specific verb and resource: it 'Find[s] a public pay-per-call tool gateway' and 'Returns connection methods.' This makes the core purpose understandable. However, it does not explicitly distinguish itself from sibling tools like weather-hint or search-query-len, which are also task-oriented, so it is clear but not fully differentiated.

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 no explicit guidance about when to use this tool versus siblings, no preconditions, and no listed alternatives. It only implies you would use it when you need a gateway for a task, but never states that explicitly or what inputs to supply. This leaves the agent to infer usage.

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