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

Without annotations, the description carries the transparency burden. It discloses that task text is discarded and certain inputs are only checked (e.g., 'no disk access', 'discarded after the shape check'), but it does not mention auth, rate limits, costs, or whether it performs network calls or side effects.

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?

Description and parameter descriptions are compact and to the point, with no unnecessary words or repetition.

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?

Tool has 9 optional parameters, no output schema, and no usage examples. The description says 'returns connection methods' but does not specify the return structure, error behavior, or how to select which parameter to pass; this leaves important context missing.

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?

Every parameter has a description with type and handling semantics (e.g., 'discarded after the length check', 'no disk access'). However, the descriptions are short and some are task-specific hints rather than full usage details.

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?

Clearly identifies the tool as a finder for public pay-per-call tool gateways and gives task examples ('weather, search, scrape, or voice'), and states it returns connection methods. The wording is slightly vague around what a 'tool gateway' or 'connection methods' are, but enough to understand the primary purpose.

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?

Does not explicitly say when to prefer this tool over sibling tools or when not to use it. It implies use for locating a gateway for tasks like weather/search/scrape/voice, but provides no direct contrast with alternatives such as weather-hint or web-fetch.

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