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

Since no annotations are provided, the description carries the burden of behavioral transparency. It states that the tool returns connection methods and discards task text, implying a read-only lookup with no side effects on inputs. However, it does not mention potential side effects, authentication requirements, or rate limits, so transparency is only partial.

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 a single sentence that packs the essential purpose, task examples, and a behavioral note into a compact form. No redundant or extraneous words are used.

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 no output schema, the description only says 'Returns connection methods,' which is vague about the exact structure of the result. It also doesn't specify how the optional parameters influence the gateway chosen, or what happens when multiple or none are provided. This is adequate for a simple index tool, but not fully complete.

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 have descriptive annotations (e.g., 'IANA timezone name' for zone, 'HTTPS URL to normalize or cite' for url) that go beyond the bare parameter names. However, the descriptions do not explain how each parameter relates to the gateway selection—for instance, how 'city' maps to a weather gateway—so the semantic connection to the tool's purpose is missing.

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 primary function: to find a public pay-per-call tool gateway for tasks like weather, search, scrape, or voice, and return connection methods. It also mentions that task text is discarded. However, it does not explicitly distinguish itself from the many sibling tools that perform these specific tasks, so it is not as sharp as it could be.

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 gives examples of tasks (weather, search, scrape, voice) that hint at when to use this tool, but it does not explicitly state when not to use it or how it relates to sibling tools. For instance, it doesn't clarify whether this should be used instead of directly calling a specific tool 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.