buildx_imagetools_inspect

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

Annotations already mark it read-only and non-destructive. The description adds important behavioral context: it uses the docker CLI's credential store, supports OCI indexes/attestations, and explains how `raw`/`format` change the output. It could mention whether a daemon is required, but the added value is substantial.

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 well-structured: a one-sentence purpose, a comparative context paragraph, a concise args list, and a return contract. No redundant sentences; each part earns its place.

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?

Given the read-only nature, 4 parameters, and no output schema, the description covers the essentials: purpose, parameter meanings, return dict, and raw/format behavior. It lacks explicit error conditions or prerequisites like buildx installation, but is still fairly complete for an inspect tool.

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 0% coverage, but the description documents all four parameters: image with concrete examples, raw and format with their semantics and mutual exclusivity, and builder as an override. This fully compensates for the schema's silence.

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?

Explicitly states the action and resource: 'Inspect a manifest in a registry without pulling.' It also distinguishes from siblings by referencing `docker manifest inspect` and `registry_manifest`, making its niche clear.

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?

Provides direct alternatives: 'Replaces `docker manifest inspect`' and '`registry_manifest` answers the same question over direct HTTPS with no daemon or plugin.' This gives clear when-to-use guidance and context for choosing between tools.

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