registry_manifest

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context beyond that: it talks HTTPS directly (no daemon/CLI), may return single- or multi-platform manifests, strips :tag/@digest from the repository string, and supports credential overrides. This enriches the behavioral model significantly.

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-line purpose, a sentence on behavior, a sentence naming alternatives, then a clear args/returns layout. No redundant wording, and each sentence carries essential information, making it easy to scan.

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 lack of output schema and 0% schema coverage, this description provides everything needed: the action, the variation in results, the transport mechanism, parameter details, and the exact return shape. It fully equips an AI agent to invoke the tool correctly and interpret results.

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 fully compensates with detailed per-parameter explanations. It clarifies that the repository string strips :tag/@digest and that reference should be used instead, explains reference as 'Tag or digest', and details username/password override semantics. This goes well beyond the bare 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?

The description opens with 'Fetch a repository's manifest without pulling', which clearly specifies the verb (fetch) and resource (repository manifest). It also distinguishes itself from sibling tools by naming direct alternatives (buildx_imagetools_inspect, image_registry_data) and noting its unique HTTPS-direct approach.

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?

Explicitly states when to use this tool versus alternatives: 'Alternatives for the same question: buildx_imagetools_inspect (uses the docker CLI and its credential store) and image_registry_data (asks the daemon).' This gives clear comparative guidance and highlights the no-daemon advantage, helping an agent choose correctly.

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