get_regions

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

The description implies a read-only operation by stating 'Retrieve', but it does not disclose any behavioral traits beyond that. Without annotations, the description could mention if the list is complete, paginated, or if there are rate limits. It provides minimal insight into the tool's behavior.

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, concise sentence with no wasted words. It is front-loaded with the key verb and resource, making it easy to parse quickly.

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?

Given the simplicity of the tool (no parameters, no output schema), the description is functional but lacks context. It does not explain what a 'region' is in EVE Online or if there are any limitations (e.g., only certain regions). It is minimally complete for its complexity.

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 has no parameters, and schema description coverage is 100% (trivially). The description does not need to add parameter info. Per the guidelines, zero parameters sets a baseline of 4, and the description is adequate here.

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 that the tool retrieves a list of regions from the EVE Online API. It uses a specific verb ('Retrieve') and resource ('list of regions'), making the purpose straightforward. However, it does not explicitly differentiate from sibling tools like 'get_region_info' or 'get_region_history', which could cause confusion about the scope.

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?

There is no guidance on when to use this tool versus alternatives. With many sibling tools that also retrieve data, the description lacks context on when 'get_regions' is the appropriate choice, such as for getting all regions vs. a specific region.

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