image_push

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

Discloses that `auth_config` carries credentials which 'many MCP clients log verbatim' – a behavioral trait beyond annotations. Annotations only give readOnlyHint and destructiveHint, so description adds important context about data exposure.

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?

Four sentences: purpose, security warning, args list, return type. Every sentence adds value, no redundancy, and critical information is front-loaded.

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 purpose, security context, parameter details, and return type. Output schema exists so return value is adequately specified. Complete for a push operation 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?

Schema has 0% description coverage (no parameter descriptions in JSON schema). The description explicitly lists `repository`, `tag`, and `auth_config` with explanations, fully compensating for the missing schema information.

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 'Push an image or repository to a registry.' This is a specific verb+resource that distinguishes from sibling tools like `image_pull`, `image_build`, etc.

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 explicit security guidance: prefer `docker login` on the host to avoid logging credentials, and leave `auth_config` unset. This tells when to use an alternative approach and how to use the tool safely.

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