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

No annotations are provided, so the description carries the full burden. It discloses it returns connection methods and discards task text, but the latter is confusing because there is no task-text parameter. It omits authentication needs, rate limits, side effects, and output format.

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 two short sentences with zero fluff. The primary purpose is front-loaded, followed by behavior notes. It is efficiently structured.

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?

For a 9-parameter tool with no output schema and no annotations, this description is inadequate. It doesn't explain how to choose parameters for a given task, what 'connection methods' entail, or why task text is discarded. An agent would struggle to call it 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%, so each parameter has its own description. The tool description adds only the task examples but does not map specific parameters (e.g., city for weather, query for search) to those tasks. It does not enhance meaning beyond the schema.

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 the tool finds a public pay-per-call tool gateway for tasks like weather, search, scrape, or voice, and returns connection methods. It distinguishes itself as a meta-tool, but doesn't explicitly contrast with sibling hints like weather-hint or search-query-len.

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 provides examples of task types (weather, search, scrape, voice) implying when it might be used, but gives no explicit when-not or alternatives. An agent would not know whether to choose this over a specific sibling hint for a given task.

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