list_tlds

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

With no annotations, the description carries the full burden. It discloses that the operation is a read-only list and specifies the returned data (TLDs with EUR prices), but it does not mention response format, ordering, pagination, or any potential side effects. For a zero-parameter list this is minimally acceptable but not richly transparent.

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?

A single, compact sentence that front-loads the verb and object and includes only the essential qualifier ('with EUR prices'). Every word earns its place; there is no redundancy or filler.

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 simple zero-parameter list tool, the description is nearly complete: it names the action and the result content. It omits an explicit return format (e.g., array of strings vs objects), but the low complexity and clear purpose mean an agent can invoke it correctly without additional details.

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 tool has zero parameters, so the description adds no parameter meaning beyond the empty schema, but none is needed. The baseline for 0 parameters is 4, and the description correctly makes no parameter claims.

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 uses a specific verb ('List') and a precise resource ('all TLDs') with a qualifier ('with EUR prices') that clearly distinguishes it from siblings like search_domain, list_products, and whois_lookup. It fully states what the tool does without ambiguity or tautology.

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 intended use is implied: call this when you need a catalog of TLDs with EUR prices. None of the sibling tools provide TLD listing, so there is no direct alternative, but the description does not explicitly state when to use it or when not to, leaving the guidance implicit.

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