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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'high-resolution images' and does not clarify whether the tool returns URLs, binary image data, multiple images, or any required permissions. The read-only nature is implied but not explicitly disclosed.

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 short phrase with no filler words. The key qualifier 'high resolution' is front-loaded and there is nothing redundant, making it very 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 one-parameter tool with no output schema or annotations, the description omits essential call-time information: what the response structure is, whether multiple images are returned, and what the 'id' parameter represents. An agent would struggle to invoke this confidently based on the description alone.

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 schema has a single 'id' parameter with no description, and the tool description does not explain that 'id' refers to the machine or what format is expected. With 0% schema description coverage, the description fails to compensate, leaving parameter meaning to be guessed from the tool name.

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 identifies a specific resource—high-resolution machine images—and the image focus distinguishes it from siblings like get_machine_detail. However, it is a noun phrase with no explicit verb like 'retrieves' or 'returns', so it does not fully meet the top tier.

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?

No guidance is provided on when to use this tool versus alternatives such as get_machine_detail or search_machines. There are no conditions, exclusions, or alternative tool mentions, so the agent must infer usage from the name and phrase alone.

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