iaas_get_compute_nat

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description contributes nothing beyond the name and HTTP path — no note on what a Compute NAT is, error behavior for unknown IDs, or response shape.

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?

Very short and front-loaded, but the first two lines say the same thing ('Get a Compute Nat' / 'Get Compute Nat with a given id'), so one of the three lines is pure repetition.

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 tool with full annotations and 100% schema coverage this is close to sufficient, but a one-clause explanation of what a Compute NAT resource represents would round it out. No output schema exists, so nothing is owed on return values.

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 path parameter and apiVersion are documented structurally. The description only restates that an id is required and adds no syntax or format detail beyond the schema.

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 and resource ('Get a Compute Nat with a given id') plus the underlying endpoint, so an agent knows this is a single-resource read. It does not distinguish itself from nearby siblings such as iaas_get_compute_nats (list), iaas_create_compute_nat, or iaas_reconfigure_nat.

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?

'with a given id' implies usage — fetch one existing Compute NAT when its ID is known — but no explicit when-to-use, when-not-to-use, or alternative (e.g. use iaas_get_compute_nats to discover IDs) is given.

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