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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions that task text is discarded and that connection methods are returned, but it does not reveal side effects, whether network calls are made, authentication needs, rate limits, or what happens to the provided parameters beyond the discard hints in the schema. This is minimal transparency.

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 two short sentences and is front-loaded with the main purpose. It is concise and avoids extraneous detail. However, the brevity contributes to the lack of clarity in other dimensions, so it is not a perfect score, but structurally it is efficient.

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 9 optional parameters, no output schema, and no annotations, the description is woefully insufficient. It does not explain the return format ('connection methods'), how the parameters influence the result, or what the tool does with each parameter. The examples of tasks are not mapped to the schema, leaving an agent with little to go on. It is a complex tool with a minimal description.

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?

Schema coverage is 100% and each parameter has a description, so the baseline is 3, but the tool description adds no meaning to the parameters. It does not explain how parameters like 'city' or 'url' are used to find a gateway, nor how they map to the tasks (weather, search, etc.). The description leaves the relationship between the parameters and the tool's purpose unexplained, which is a significant gap.

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 specific verb ('find') and resource ('public pay-per-call tool gateway'), with example tasks (weather, search, scrape, voice). However, it does not clarify how the parameters (e.g., city, url, query) relate to the task or how the task is specified. It does not distinguish from sibling tools like weather-hint or web-fetch, leaving the exact purpose ambiguous.

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?

No guidance on when to use this tool versus alternatives. There is no mention of when not to use it, no prerequisites, and no comparison with sibling tools. The description does not help an agent decide between this and tools like geo-hint or search-query-len.

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