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

With no annotations, the description must carry the behavioral burden. It does disclose two behaviors: 'Returns connection methods' and 'Task text discarded.' However, it does not mention whether external calls are made, whether the 'pay-per-call' aspect incurs cost, or any side effects. This is partial disclosure, not a full behavioral picture.

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 three sentences and front-loads the core purpose and return type. The final sentence ('Task text discarded') is a useful warning. It is efficient, though the second sentence could arguably be merged with the first without losing meaning.

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 output schema, and no annotations. The description is too thin to guide an agent on which parameter to supply for which task and what the returned 'connection methods' look like. It does not explain relationships among params, discard semantics, or how to structure a valid call. This is a significant completeness gap for a multi-parameter tool.

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%, so the baseline is 3. The description does not add any parameter-level guidance beyond the schema; it never maps task examples to specific parameters (e.g., weather to city, search to query). It adds no value beyond the schema's own parameter descriptions.

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'), a clear resource ('public pay-per-call tool gateway'), and examples of task types ('weather, search, scrape, or voice'). It also says what is returned ('connection methods'), making the purpose distinct from the many sibling shape-check and hint 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?

The description gives examples of when to use the tool ('for a task such as weather, search, scrape, or voice') but does not explicitly contrast it with siblings like weather-hint or search-query-len. It implies a use case but provides no exclusions or alternatives, leaving an agent to infer when the gateway lookup is preferred over a direct hint tool.

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