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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds that images are high-resolution and include both gallery and cover versions, which is useful content context. However, it does not disclose other behaviors such as response format or error handling, so it provides only moderate added value beyond 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?

The description is a single concise sentence that immediately states the core content and purpose. There is no filler or redundancy; every phrase contributes meaningful information.

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?

The tool is simple (one parameter, read-only) and has an output schema (not shown but indicated), so return structure is documented elsewhere. The description covers what images are included and their intended use, which is sufficient for an agent to invoke correctly. Minor gap: it does not explicitly state that 'id' refers to a machine identifier, but this is inferable from the tool name and sibling context.

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 0%, so the parameter 'id' has no schema-level explanation. The description does not mention the id at all, leaving the agent to infer it refers to a machine identifier from the tool name. This fails to compensate for the missing schema description, making the parameter semantics unclear for an agent unfamiliar with the domain.

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 a specific resource (machine images) with modifiers (high resolution, gallery + cover) and enumerates use cases (cards, comparisons, publications, presentations). This clearly distinguishes it from siblings like get_machine_detail or search_machines, which serve different purposes.

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 gives clear context on when to use the tool by listing concrete use cases (cards, comparisons, publications, presentations). It does not explicitly mention alternatives or exclusions, but the stated purpose is sufficiently directive for an agent to infer appropriate usage.

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