registry_inspect_manifest

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

Description adds context beyond annotations: may return single or multi-platform manifest, image argument strips tag/digest, optional credential override. No contradiction with readOnlyHint/destructiveHint.

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?

Efficiently structured: purpose sentence, behavior note, then args list, then returns. No unnecessary detail, every sentence adds value.

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?

Covers input, behavior, and return structure (dict keys). Lacks error handling details, but tool is simple and annotations are sufficient. Missing explicit mention of auth failure or image not found.

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?

All 4 parameters are described with examples and defaults (e.g., image stripping, reference default 'latest', username/password override). Schema coverage is 0%, so description fully compensates.

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?

Description states 'Fetch the manifest for an image reference without pulling' with a clear verb and resource. It distinguishes from pulling actions and is unambiguous among siblings.

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?

Includes 'without pulling' to indicate use case and explains possible return types. Does not explicitly list alternatives or when-not-to-use, but context is clear.

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