Get detailed information about a specific image build.

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

Discloses that the tool is read-only (consistent with readOnlyHint annotation) and idempotent (openWorldHint). Adds behavioral context: returns detailed status, error messages, download URLs, logs, artifact details. No contradictions with annotations.

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?

Description is well-structured with emoji markers and sections, making it easy for an AI to parse. Slightly verbose with repetitive warnings, but every sentence adds value and the structure enhances usability.

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 tool's simplicity (one parameter, read-only retrieval), the description fully covers purpose, prerequisites, common mistakes, and return content. Output schema exists for return values, so no need to detail them.

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 'compose_identifier' is fully described in the schema as 'exact UUID string from get_composes()'. The description reinforces this with examples of what NOT to use and emphasizes the prerequisite step.

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?

Title and description clearly state 'Get detailed information about a specific image build' using a specific verb and resource. The description distinguishes from sibling tools like get_composes and get_blueprint_details by explicitly requiring the compose UUID from get_composes().

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 step-by-step process: call get_composes() first to get UUID, then call this function. Warns against using generic terms like 'latest' and states when to use (user asks about build status). Clearly differentiates from alternatives.

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