Get detailed information about a specific image build.

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

Annotations already mark as read only and open world. Description adds specific return details (status, progress, errors, download URLs, logs) and process context, but no contradictions.

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?

Well-structured with sections for requirements, warnings, process, and returns. Every sentence adds value. Front-loaded with purpose.

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 low complexity, 100% schema coverage, output schema present, and annotations, the description fully covers prerequisites, process, and return values.

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 coverage is 100%. Description adds crucial meaning: parameter must be exact UUID from get_composes(), not generic terms. This goes beyond schema documentation.

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 title and description explicitly state it gets detailed info for a specific image build. It distinguishes from siblings like get_composes (list) and get_blueprint_details by requiring a UUID.

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?

Provides explicit instructions: requires compose UUID from get_composes(), warns against generic terms, and outlines a clear process from user request to function call.

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