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

The description transparently notes that task text and parameter values are discarded after the call, which informs the agent about side effects. However, it does not disclose whether the tool makes external network requests, requires authentication, or has any side effects beyond returning connection methods.

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 extremely concise, consisting of two short sentences with no redundant phrasing. It directly states the tool's primary function and a key behavioral detail, making it easy to read and quickly understand.

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 9 parameters and no output schema, the description is incomplete because it does not explain how the tool selects a gateway, what format the 'connection methods' take, or whether any of the parameters are required for certain task types. The phrase 'task text discarded' adds confusion rather than clarification, leaving significant gaps in the agent's understanding.

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?

The input schema already provides clear descriptions for all 9 parameters, each indicating its purpose and that it is discarded. The description adds little beyond the schema, mainly repeating the discarding behavior and mentioning that the tool returns connection methods, but does not clarify how parameters map to different gateway choices.

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 that the tool finds a public pay-per-call gateway for tasks like weather, search, scrape, or voice, and returns connection methods. However, it is vague about how the gateway is selected and what 'task text discarded' means in practice, leaving some ambiguity.

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?

It lists example task categories (weather, search, scrape, voice) but provides no explicit guidance on when to use this tool over the many sibling tools (e.g., weather-hint, search-query-len). There is no mention of prerequisites, alternatives, or conditions that would make this the preferred choice.

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