push_plugin

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

With annotations showing readOnlyHint=false and destructiveHint=false, the description adds that it pushes to a remote registry, requires prior auth, and returns push progress/status events. No contradictions.

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 covering action, prerequisites, parameter details, and return value. No fluff; every sentence is necessary and informative. Information is well-structured and 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?

Given the tool has a single required parameter and no output schema, the description covers all necessary aspects: what it does, prerequisites, parameter format, and return type. Sufficient for correct use.

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 one parameter 'name' with no description. The description fully compensates by explaining the format (include registry host if not Docker Hub, include tag) and gives examples like 'registry.example.com/myplugin:1.0' and 'myorg/myplugin:latest'.

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 starts with a clear action and resource: 'Push a locally built or pulled plugin image to a remote registry.' This is specific and distinguishable from sibling tools like push_image or install_plugin.

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 authentication requirement and suggests calling 'login' first. Also explains naming rules for registry hosts. Does not explicitly state when not to use, but provides sufficient context for correct invocation.

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