portainer_image_pull

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

No annotations are provided, so the description carries full behavioral transparency burden. It explains the action (pull) and key parameter effects but does not disclose potential side effects like disk usage, network requests, or how authentication failures are handled. This is adequate but could be improved.

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 structured with a one-line summary followed by an Args section. It is efficient and front-loaded, though the Args formatting adds some verbosity. Every sentence adds value without redundancy.

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 output schema exists (context signal), the description does not need to cover return values. It covers the core purpose and parameter semantics well. However, it omits preconditions like requiring a valid endpoint or network connectivity, which would make it more complete for an agent deciding whether to invoke this 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?

With 0% schema description coverage, the description compensates fully. It explains image_name with examples, tag with default, registry_auth as optional base64 JSON with format example, and endpoint_id with fallback behavior. This adds critical meaning beyond the input schema, which only provides types and defaults.

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 'Pull a Docker image from a registry,' which clearly states the verb, resource, and context. It distinguishes from sibling tools like portainer_image_remove or portainer_images_list by focusing on the pull action.

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 provides parameter-specific guidance (e.g., registry_auth required for private registries, endpoint_id defaults if omitted). However, it does not explicitly state when to use this tool versus alternatives like portainer_container_exec or portainer_images_list, though the tool name and siblings make this largely self-explanatory.

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