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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Returns connection methods' and 'Task text discarded,' but it's unclear what 'task text' refers to since there's no corresponding parameter. It doesn't disclose side effects, network usage, cost implications (despite mentioning pay-per-call), or any rate limits. The disclosure is minimal and confusing.

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 only two sentences, front-loading the purpose and adding a behavioral note about discarded task text. It is efficient and free of fluff, earning a high score for conciseness.

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?

The tool has 9 optional parameters with no required ones, but the description doesn't clarify how an agent should specify the desired task. The phrase 'Task text discarded' is ambiguous since no task-text parameter exists, and the output ('connection methods') is undefined without an output schema. An agent lacks the information needed to call this tool 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?

The input schema provides 100% coverage with each parameter having a descriptive comment (e.g., 'City name for a public weather hint; discarded after the call'). The description itself doesn't add meaning beyond the schema; it doesn't explain how parameters relate to the task selection or what 'connection methods' mean. Baseline 3 is appropriate given the schema already documents parameters well.

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's purpose: 'Find a public pay-per-call tool gateway for a task such as weather, search, scrape, or voice.' It specifies the verb (find), resource (gateway), and gives examples. However, it doesn't explicitly differentiate itself from the many sibling tools that serve similar task domains, so it's clear but not sharply distinguished.

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?

The description implies when to use the tool (for tasks like weather, search, scrape, or voice) but provides no explicit guidance on when not to use it or how it relates to alternatives. It doesn't mention any of the sibling tools or explain that specific parameter choices select a task. An agent would struggle to know whether to use this tool versus a more specific sibling like weather-hint or validate-json.

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