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

Annotations already declare readOnly=true, destructive=false and openWorld=true, so the safety profile is covered. The description adds one behavioral note beyond that — 'OIDC settings (no secrets)' — which usefully signals redaction, but it says nothing about auth, rate limits, or missing-cluster 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?

Front-loaded with the field inventory in a single tight sentence, with the REST path appended. The path is somewhat redundant with the tool name, keeping it just short of a 5.

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?

With no output schema, the description's field enumeration usefully tells the agent what comes back, and the '(no secrets)' caveat sets expectations. It is largely complete for a one-parameter read, though it omits pagination/error behavior that a full 5 would touch.

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% with both parameters (id, zone) fully documented in the schema, so the schema carries the load. The description adds no syntax, format, or zone-selection meaning beyond it, which is the baseline-3 case.

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 ('Details of one') and resource (SKS cluster), and enumerates the exact fields returned (version, state, level, CNI, add-ons, OIDC settings, endpoint, node pools). The word 'one' cleanly distinguishes it from the sibling exoscale_list_sks_clusters.

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 only implied by the singular 'one SKS cluster' versus the sibling list tool; there is no explicit statement of when to use this versus exoscale_list_sks_clusters or any prerequisite/zone guidance. Adequate but with a clear gap.

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