Get blueprint details.

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, which cover safety and openness. The description adds that an exception is raised if the connection fails, which is useful behavioral context. No contradictions with annotations are present.

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 short and to the point, using formatting (emoji, line breaks) to highlight the immediate invocation hint. Every sentence serves a purpose, though the 'Returns' section could be more concise.

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 operation with one parameter and an output schema, the description is adequate. However, it lacks detail about what 'blueprint details' entail (e.g., fields or structure), leaving the agent to infer from the tool name and schema.

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?

The single parameter 'blueprint_identifier' is fully described in the input schema with details on acceptable formats (UUID, name, reply_id). The description adds no additional parameter semantics, and since schema coverage is 100%, a 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 states 'Get blueprint details' which is a general verb+resource but lacks specificity about what constitutes a blueprint in this context. Compared to sibling tools like image-builder__get_blueprints (listing) and image-builder__get_compose_details, the purpose is somewhat distinguished but not clearly defined.

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 description includes '🟢 CALL IMMEDIATELY - No information gathering required' which provides a usage hint about when to invoke. However, it does not explicitly contrast with alternatives or state when not to use this tool. The hint is helpful but limited.

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