blueprint_list_terraform_versions

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond the raw path — no mention of pagination behavior despite top/skip/pageable parameters, no note on what a version record contains, and no default-page-size 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 lines with the purpose front-loaded and no filler prose. The second line duplicates the endpoint string already present in the annotation title, which is mild redundancy but harmless.

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 read-only list tool with a well-described schema and annotations covering safety, the definition is minimally viable. It omits any hint of return shape or pagination envelope, which matters since there is no output schema, but nothing critical to correct invocation 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 83%, so the schema already documents top, skip, orderby, apiVersion and onlyEnabled. The description contributes no additional parameter meaning (e.g. valid orderby fields or interaction between top/skip and pageable), so the baseline of 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 and resource ('Lists terraform versions'), which is clear on its own. However, it never distinguishes itself from sibling blueprint_get_terraform_version (single fetch) or blueprint_create/update/delete_terraform_version, so an agent must infer the list-vs-get boundary from the name alone.

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 guidance on when to call this versus the singular blueprint_get_terraform_version, nor any stated preconditions. The only 'usage' signal is the embedded REST path, which describes the endpoint rather than when an agent should choose this tool.

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