image_tag

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

Annotations indicate not read-only nor destructive. The description adds parameter explanations but does not disclose side effects (e.g., overwriting existing tags) or prerequisites. It provides return type but could be more transparent about behavior.

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 concise, front-loading the main action, and lists parameters and return type efficiently. No unnecessary words.

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?

For a simple tagging operation, the description covers the essential information. It explains parameters and return value, compensating for the lack of schema descriptions. However, it could mention typical use cases or edge cases.

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?

With 0% schema description coverage, the description adds meaning by explaining each parameter (source, repository, tag, force). However, 'force' is not fully clarified (e.g., what it forces), so it's good but not exhaustive.

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 clearly states 'Tag an image into a repository', specifying the verb and resource. It distinguishes from sibling tools like image_build or image_push, which involve different actions.

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 description lacks any guidance on when to use this tool versus alternatives. No context about prerequisites, when to use force, or comparison with related tools is provided.

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