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

With no annotations, the description bears the full burden. It only says 'Task text discarded' and 'Returns connection methods,' giving no clues about side effects, permissions, or data handling. The tool could be read-only or perform external calls, but this is not addressed.

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, consisting of a single sentence with no redundant text. However, it lacks any structured breakdown of what the tool does, making it minimally acceptable.

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 varied parameters and a vague purpose, yet the description gives no details on how they interact, what kind of output to expect, or what 'connection methods' means. The absence of an output schema and the confusing parameter list make the tool highly incomplete for an agent to use correctly.

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 the schema descriptions are individually clear (e.g., 'city' as a weather hint), the tool description does not explain how these parameters relate to finding a 'tool gateway.' The parameters seem to be inputs for various sub-tasks, but their role in this tool is unexplained.

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 it 'Find a public pay-per-call tool gateway' for tasks like weather, search, scrape, or voice, which gives a general sense. However, the phrase 'Task text discarded' is confusing, and the connection between the listed parameters and the stated purpose is unclear, making the overall purpose vague.

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?

There is no guidance on when to use this meta-tool versus the many sibling tools (e.g., browser-url-ok, calc-eval). The description does not mention any conditions or context that would lead an agent to choose this tool over alternatives.

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