inspect_container

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

readOnlyHint=true already declares this as a safe read, and the '[READ]' prefix merely restates it. The description does add value by naming the returned sections (config, state, mounts, network), but omits auth requirements, size/pagination behavior, or any caveats. With annotations carrying the safety profile, this is 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 purpose is front-loaded and the Args block is compact. The '[READ]' prefix is redundant with readOnlyHint=true, a minor waste, but overall the structure is efficient and skimmable.

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?

There is no output schema, so the description usefully enumerates the inspect sections (config, state, mounts, network). For a read-only tool this is fairly complete, though it stops short of describing return structure or depth.

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, and it does: container_id accepts an id or a name (added value over the bare string type), and target is explained as a 'target name from config; omit for the default'. 'Target' remains somewhat cryptic, but both parameters receive meaningful semantics beyond the schema.

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 ('Full inspect of one container') and enumerates what it returns (config, state, mounts, network), which cleanly distinguishes it from the inspect_image/inspect_network/inspect_volume siblings. An agent can identify the target resource without opening the schema.

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 '[READ]' tag and 'Full inspect' imply a read-only diagnostic context, but there is no explicit when-to-use guidance or contrast with list_containers, container_stats, or container_logs. Usage is only implied.

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