List Akamai Edge Locations

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

With no annotations, the description carries full responsibility. It clearly indicates a read-only list operation and mentions the output format (location IDs), but does not disclose potential large result sizes, ordering, or any other behavioral nuances. It provides basic transparency without surprises.

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?

Two sentences, front-loaded with the main action, with no wasted words. Every sentence earns its place: the first states the core purpose, the second explains the output's downstream utility.

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 parameterless, list-only tool with no output schema, the description is fully complete. It states what it lists and why the results matter, making it enough for an agent to use it 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 tool has zero parameters, so the baseline is 4. The description adds value by explaining the return value (location IDs) and how they are used, which is relevant for invoking the tool correctly even though no parameters exist.

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 opens with a specific verb ('Lists') and resource ('Akamai edge server locations'), clearly distinguishing it from sibling tools that perform translations, checks, or diagnostics. It also states the output's purpose: providing location IDs for use in other tools.

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 the typical use case ('Returns location IDs that can be used as edgeLocationId in other tools'), giving context for when to call it. It does not explicitly exclude alternatives, but since no sibling tool is similar, this is clear enough.

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