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

There are no annotations, and the description does not disclose side effects, costs, permissions, or network access. The repeated 'discarded' hints suggest the tool performs no persistent actions, but this is not explicit. The term 'pay-per-call' implies potential charges, yet no warning or clarification is given.

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 and follows a straightforward structure: two short sentences that state the purpose and a caveat. It avoids unnecessary fluff and gets to the point quickly, though the brevity contributes to ambiguity in other dimensions.

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?

Given the tool's complexity (9 optional parameters, no output schema, no annotations), the description is insufficient. It does not explain how the parameters are used together, what the expected output format is, or provide any example call. An agent would struggle to construct a meaningful request without additional context.

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 schema descriptions cover all 9 parameters, they are inconsistent and misleading. For example, 'City name for a public weather hint; discarded after the call' suggests the parameter is used as a hint but then discarded, and 'Search text; discarded after the length check' implies it is only used for validation. The descriptions do not clarify how these parameters relate to the tool's core function of finding a gateway, leaving the actual semantics unclear.

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 the tool's primary function: 'Find a public pay-per-call tool gateway for a task such as weather, search, scrape, or voice.' This provides a clear verb (find) and resource (gateway), but the phrase 'Task text discarded' is ambiguous and could confuse the reader about what input is actually used.

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 guidance is provided on when to use this tool versus alternatives. The sibling-tools list includes many related tools (e.g., weather-hint, search-query-len, validate-json), but the description does not mention any of them or explain how this index differs. Thus, an agent cannot determine when to prefer this tool over others.

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