tag_image

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

No annotations are provided, so the description bears the full burden of behavioral disclosure, and it discloses nothing. It does not say whether tagging requires prior image existence, whether the tag must be unique, whether it mutates the image record, or what happens on conflict.

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?

Two words is not conciseness but under-specification; there is no wasted text because there is almost no text. The description fails to front-load any information an agent needs.

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 mutation tool requiring three mandatory parameters, with no annotations and no output schema, the description is completely inadequate. It leaves the agent unable to determine preconditions, side effects, or the meaning of any input field.

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?

Three required parameters (id, tag, repo) have 0% schema description coverage, and the description adds no meaning for any of them. An agent must guess what 'id' identifies, whether 'repo' is a registry or local namespace, and the expected tag format.

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 is essentially a restatement of the tool name 'tag_image' ('Tag image'), adding no scope, target, or distinguishing detail. An agent cannot tell from this text whether it tags a local image, applies a tag to a registry reference, or how it differs from siblings like commit_container or push_image.

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?

There is no guidance on when to use this tool versus alternatives such as commit_container, build_image, or push_image. The verb+resource does at least imply the general operation, but no context, prerequisites, or exclusions are given.

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