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

No annotations are provided, so the description must disclose behavior. It only mentions 'Task text discarded' and that parameters are 'discarded after the shape check,' but it does not explain side effects, permissions, rate limits, or whether the tool modifies any state. The lack of detail makes behavior opaque.

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 short but unstructured, consisting of a single vague sentence with no clear breakdown of purpose, behavior, or examples. It lacks a logical flow and does not effectively organize the information needed to understand the tool.

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 complexity of 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not specify the format of 'connection methods,' error conditions, or how the parameters influence the result, leaving essential context missing.

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 parameters, they are terse and often state the value is 'discarded after the shape check' or 'no disk access,' implying the parameters are only validated, not used meaningfully. The relationship between parameters and the returned 'connection methods' is undefined, making it unclear how to provide useful input.

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 'finds a public pay-per-call tool gateway' for tasks like weather, search, scrape, or voice, but it does not clarify what a 'tool gateway' is or how the input parameters relate to the task. The phrase 'Returns connection methods' is vague, and the tool's exact functionality remains ambiguous.

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 tool versus the listed sibling tools. It does not mention prerequisites, context, or any decision criteria for selecting this tool over alternatives, leaving users without direction.

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