iso_get_iso

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get details,' which implies a read operation, but it does not disclose authentication needs, behavior when the ISO is not found, or error handling. For a retrieval tool with zero annotation coverage, this is a notable gap.

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 brief with a clean Args/Returns structure and no wasted words. However, the brevity is a result of under-specification rather than deliberate efficiency; the Returns section merely repeats the purpose rather than adding detail.

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?

An output schema exists, so return values need not be elaborated. For a single-parameter get tool the description is functionally adequate, but it omits distinguishing guidance versus the by-name sibling and any behavioral caveats, leaving the definition minimally sufficient.

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 description must compensate, but it merely restates the parameter ('iso_id: The ISO ID'), adding no meaning beyond the schema's type definition. There is no format, validation rule, or context for what constitutes a valid ISO ID.

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 verb and resource: 'Get details of a specific ISO image.' This clearly conveys the operation. However, it does not distinguish itself from the sibling iso_get_iso_by_name, which performs the same retrieval by a different key, so differentiation is left to inference from the tool names.

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?

There is no guidance on when to use this tool versus alternatives. The sibling iso_get_iso_by_name exists for retrieving ISOs by name rather than ID, but the description never mentions this or any conditions that would select one over the other. An agent must infer the usage distinction from naming alone.

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