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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are scoped per zone and lists returned fields, but doesn't disclose pagination behavior (limit/offset semantics) or the API endpoint caveat that the API returns whole lists despite limit/offset parameters.

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?

Single efficient sentence that front-loads the verb/resource and then enumerates returned fields, followed by the endpoint. No wasted words; slightly dense but appropriate.

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 list tool with annotations covering safety and full schema coverage, the description is adequate. It lacks pagination guidance and the 'API returns whole lists' nuance that would help an agent call it correctly across pages. No output schema, so return-field enumeration is a plus but not a substitute for behavioral detail.

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?

Schema coverage is 100%, so the schema fully documents zone, limit, and offset including defaults and enum values. The description adds no parameter-specific detail beyond 'of a zone', so baseline 3 is appropriate.

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?

States a specific verb (List) and resource (SKS clusters) and enumerates the returned fields. It distinguishes from exoscale_get_sks_cluster by saying 'clusters' (plural list) but doesn't explicitly contrast the singular get sibling.

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?

Usage is implied by 'List the SKS clusters of a zone' — the zone parameter scopes the query. However, no explicit guidance on when to use this vs exoscale_get_sks_cluster or the other list_* tools, and no mention that it requires a zone context.

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