Show user's image blueprints (saved image templates/configurations for

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

Annotations already declare `readOnlyHint` and `openWorldHint`, indicating a safe, read-only operation. The description adds minimal behavioral context beyond the content of blueprints. It does not discuss pagination or other behavioral traits, but annotations reduce the burden.

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?

The description is extremely concise with only two lines, front-loading the main purpose and including a clear call-to-action. No wasted words.

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?

Given the presence of output schema and full parameter descriptions, the description is largely complete. It could clarify that this returns a list of all user-owned blueprints, but the title and sibling tool hint at that.

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 the description does not add any parameter-specific meaning beyond what the schema already provides. Baseline score of 3 is 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 clearly states that the tool shows the user's image blueprints, and enumerates their contents (Linux distributions, packages, users). It distinguishes from the sibling `get_blueprint_details` by implying this is a list of all blueprints.

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?

The instruction 'CALL IMMEDIATELY - No information gathering required' provides a usage prompt, but there is no explicit discussion of when not to use this tool or alternatives. The agent must infer from context that `get_blueprint_details` is for a specific blueprint.

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