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

No annotations, so the description must carry the burden. It says inputs are discarded after checks and returns connection methods, but doesn't mention costs, side effects, or what 'gateway' entails.

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 and front-loaded with a clear verb and object. Parameter descriptions are terse, though repetitive.

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?

No output schema and no required parameters; the description doesn't specify the shape of 'connection methods' or how the optional parameters relate, leaving significant ambiguity.

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?

All nine parameters are described, but most descriptions are odd and only state that the value is discarded after a shape/length check, without explaining how each parameter is used to find the gateway.

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?

States it finds a public pay-per-call tool gateway for sample tasks and returns connection methods, but the wording is vague and doesn't clearly distinguish it from many sibling 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?

Mentions example tasks (weather, search, scrape, voice) but gives no explicit guidance on when to choose this tool over alternatives like weather-hint or search-query-len.

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