blueprint_list_blueprint_versions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds nothing beyond restating the endpoint URL, which duplicates the annotation title, and says nothing about pagination defaults, result ordering, or empty results for a 12-parameter listing operation.

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, which is good, but the second line is redundant with the annotation title and carries no information the agent cannot already see. It is terse without being efficiently 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 12-parameter paginated listing tool with no output schema, the description says nothing about the shape of the returned list, pagination conventions (skip/page/size interplay), or default sort behavior. The schema covers parameter names, but the description leaves the operation's result semantics entirely implicit.

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%, including the enum for status and the documented ordering fields, so the weighted baseline of 3 applies. The description contributes no additional meaning about how pagination, sort, or version filters interact.

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 blueprint versions') and gives the backing REST endpoint, so the agent knows exactly what it returns. It does not differentiate from the sibling blueprint_get_blueprint_version, relying on the list/get naming distinction 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?

No statement of when to use this instead of blueprint_get_blueprint_version or blueprint_list_blueprints, and no prerequisites or exclusions. The only hint is the raw endpoint path, which implies a collection read but does not guide selection.

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