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

With no annotations, the description carries full responsibility for explaining side effects and constraints. It only says 'Returns connection methods' and 'Task text discarded,' which does not disclose actual behavior, failure modes, or how parameters influence the result.

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 concise and has no redundant fluff, but its brevity sacrifices clarity. The phrase 'pay-per-call tool gateway' is awkward and the overall structure leaves the reader guessing what the tool actually does.

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?

There is no output schema and no mention of errors, return format, or how to interpret 'connection methods.' Given the tool's apparent meta-nature and nine parameters, the description is far too sparse to be considered complete.

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 all parameters have descriptions, they are largely nonsensical or dismissive ('discarded after the shape check', 'no disk access'). They do not explain how each parameter is used to find a tool gateway, so the high schema coverage does not translate to real 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 says it 'Find[s] a public pay-per-call tool gateway' but this is vague and the connection to parameters like ref, host, zone, or query is unclear. It does not clearly distinguish the tool's core function from the many sibling tools.

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 lists example task types ('weather, search, scrape, or voice') but gives no concrete guidance on when to choose this tool over alternatives. No sibling tools are mentioned, and the 'task text discarded' line adds confusion rather than clarifying usage.

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