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

With no annotations provided, the description is responsible for behavioral disclosure, and it does disclose some: 'Returns connection methods' and 'Task text discarded.' This tells the agent the tool is a lookup/directory and that inputs are not retained. However, it leaves out other behavioral details such as whether any external calls occur, performance characteristics, or what exactly a 'connection method' string/list looks like.

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 compact and front-loaded: the first sentence names the purpose, and the follow-up sentence adds the useful discard/discard behavior and output summary. Each of the three sentences earns its place, with no redundant or filler wording.

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?

This is a 9-parameter, optional-complex tool with no output schema and no annotations, yet the description provides only a one-line summary and a discard note. It does not explain how to select or combine the optional parameters to influence the lookup, what the 'connection methods' actually look like, or how to interpret a successful/failed call. The agent needs more to call this tool effectively.

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 description coverage is 100%, and each parameter already carries its own description, so the baseline is 3 even though the tool description itself does not explain parameters. The description's task examples (weather, search, scrape) hint at some parameter mappings (city, query, url), but it does not explicitly connect them to the schema fields.

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 clearly states a specific action and resource: 'Find a public pay-per-call tool gateway' for task types like weather, search, scrape, or voice. It also says it 'Returns connection methods,' which clarifies a distinct goal from just performing the task. However, it does not explicitly distinguish these from the sibling tools (e.g., weather-hint or search-query-len), leaving some differentiation to inference.

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 explicit guidance on when to use this tool versus the many siblings, nor any 'when not to use' or alternative tooling. The examples in the description imply a use case ('for a task such as weather...'), but that is too thin to serve as practical selection guidance among similar-looking tools.

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