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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned field list and HTTP method, but does not disclose error behavior, authentication requirements, or rate limits, which would be the remaining useful behavioral context.

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 with zero waste. The purpose and returned fields are front-loaded, and the trailing endpoint reference is compact and informative.

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 read-only retrieval tool with full schema coverage and annotations that carry the safety profile, this description is sufficient. It tells the agent what the tool does, what it returns, and the underlying endpoint, with no output schema needed to supplement it.

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 description coverage is 100%, so both the id pattern and the zone enum/default are already documented in the schema. The description adds no additional meaning about parameter usage or format beyond what the schema provides, making the baseline 3 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?

The description states a specific verb and resource ('Details of one elastic IP') and explicitly scopes it to a single resource, which cleanly separates it from the sibling exoscale_list_elastic_ips. It also names the exact fields surfaced (address, CIDR, family, description, health check, labels), so an agent knows precisely what this tool returns.

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 the singular scope and the 'GET /elastic-ip/{id}' endpoint, but there is no explicit guidance on when to choose this over exoscale_list_elastic_ips or other exoscale_get_* tools. No prerequisites, exclusions, or alternative-selection criteria are stated.

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