blueprint_get_terraform_version

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond restating the endpoint path — no note on what is returned, error behavior for a missing versionId, or any auth/scope 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 short fragments, front-loaded with the purpose. The REST path line is largely redundant with the annotation title, but the overall entry is tight and wastes little.

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 getter with full schema coverage and complete annotations, this is minimally sufficient. However, with no output schema, the description could say what a Terraform version record contains or how it relates to blueprint versions, which is missing.

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 versionId (uuid path param) and apiVersion are already documented in the schema. The description mentions the versionId path segment but adds no format, sourcing, or versioning guidance beyond it, so baseline 3 applies.

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 ('Returns') and resource ('Terraform Version details'), which distinguishes it from blueprint_list_terraform_versions, blueprint_create_terraform_version, and blueprint_delete_terraform_version. It does not explicitly name those siblings, but the singular retrieval purpose is unambiguous.

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?

There is no statement of when to use this tool versus the list/create/update/delete Terraform version siblings, nor any prerequisite or context. Only the tool name and REST path imply it is a single-resource fetch.

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