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

With no annotations provided, the description must disclose behavioral traits. It mentions 'Task text discarded' and 'Returns connection methods', but says nothing about side effects, cost implications (pay-per-call), or what happens to the parameters (many schema descriptions say 'discarded after', but the main description does not state that). The tool appears to be read-only, but that is not explicitly stated.

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 very brief, two sentences, and leads with the core purpose. There is no extraneous text. However, the brevity comes at the cost of missing essential guidance, but for conciseness alone, 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?

The tool has 9 optional parameters, no annotations, and no output schema, yet the description provides almost no contextual completeness. It does not explain how to invoke the tool, what the 'connection methods' look like, or how the parameters map to the task. An agent would have no idea what to pass or what to expect back, making this seriously inadequate for a tool with such a broad parameter set.

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 the input schema provides 100% parameter descriptions, the tool description adds no context on how these parameters relate to the stated purpose. The parameters (city, feed, host, json, path, zone, query, etc.) seem unrelated to 'finding a gateway' and appear to be validation inputs for other tools. The description does not bridge this gap, so an agent cannot infer which parameters are relevant for a given task.

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 action ('find a public pay-per-call tool gateway') and a resource type, but it is vague about how the tool actually accomplishes this. It lists example tasks (weather, search, scrape, voice) without mapping any of the 9 input parameters to those tasks, leaving the agent unsure of what to supply. The phrase 'Task text discarded' adds a constraint but does not clarify the core purpose.

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 guidance on when to use this tool versus the many sibling tools (e.g., weather-hint, search-query-len). It does not mention alternatives or provide conditions for selection. The only contextual hint is the list of example tasks, but it does not explain how this index relates to the dedicated per-task tools.

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