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

No annotations are provided, so the description carries full burden. It states 'Returns connection methods' and 'Task text discarded', but does not disclose whether the tool makes external calls (despite 'pay-per-call' hinting at cost), what side effects exist, or how the input parameters are processed. The parameter descriptions in the schema suggest validation-only behavior, but the tool description contradicts this by implying an external gateway lookup. This lack of clarity is a significant gap.

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 (two sentences) and front-loaded with the primary purpose. However, it omits crucial information about how the parameters are used, what 'connection methods' means, and how it differs from sibling tools. It is under-specified rather than efficiently concise, so a score of 3 reflects that it is brief but not adequately informative.

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?

With no output schema and no annotations, the description is the only source of context. It fails to explain the return format (beyond 'connection methods'), how to map the 9 optional parameters to specific tasks, any prerequisites, or limitations. Given the complexity of 9 parameters and no annotations, the description is severely incomplete for an agent to call this tool 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?

Schema description coverage is 100% and each parameter has a clear, self-contained description (e.g., 'Git ref name; discarded after the shape check', 'HTTPS URL to normalize or cite'). The tool description adds no additional meaning beyond the schema; it actually introduces a non-existent 'task text' parameter, which could confuse. Baseline 3 is appropriate since the schema does the heavy lifting, but the description fails to bridge parameters to the tool's stated purpose.

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 verb ('Find') and resource ('public pay-per-call tool gateway') for tasks like weather, search, scrape, or voice. It is distinct from sibling tools which appear to be specific checks/hints. However, it does not explain how the parameters relate to this purpose, leaving some ambiguity about what the tool actually does.

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 explicit guidance on when to use this tool vs alternatives. It implies a use case (finding a gateway for a task) but does not mention when not to use it, which sibling tools are alternatives, or how the optional parameters should be provided for different tasks. The mention 'Task text discarded' adds confusion rather than guidance.

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