iso_inspect

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

With no annotations, the description carries the full behavioral burden. It does convey the important trait that nothing is mounted and the read is pure ISO9660/Joliet, implying a non-destructive inspection, but it says nothing about permissions required, side effects, or cost. Adequate but not rich.

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 value proposition is front-loaded in the first sentence, followed by the when-to-use context and the routing note. Three tight sentences with no filler, though the version-marker detail could be folded more economically.

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 no explanation. For a two-parameter read-only inspection tool the description covers purpose, timing, expected findings, and a hand-off to fingerprint_windows; only the parameter meanings are missing.

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%, and the description mentions neither iso_path nor max_entries. In particular the max_entries default of 300, which governs how much of the listing is returned, is left completely unexplained, so agents cannot anticipate truncation.

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?

States a specific verb and resource (list an install ISO's contents) plus the key constraint 'WITHOUT mounting it', which immediately separates it from vm_mount_iso and iso_extract. The parenthetical 'pure ISO9660/Joliet read' adds precision that an agent can use to distinguish it from sibling ISO tools.

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?

'Use this before any VM work' gives a clear precondition, and it names fingerprint_windows as the alternative for the full version verdict. It does not explicitly distinguish itself from the nearest siblings iso_verify, iso_extract, or vm_mount_iso, so routing among those is left to inference.

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