arcane_pull_image

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

With no annotations, the description must disclose behavioral traits, but it only states the action. It does not mention side effects (e.g., image downloaded to environment, may overwrite existing tags, requires registry credentials, network/disk usage). This is a significant transparency gap.

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 a single sentence with no wasted words, well-suited for a concise tool description. However, it is almost too minimal, lacking context that could be added without much bulk.

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?

Despite having 5 parameters and no output schema, the description provides no information about return values, errors, or destination of the pull (e.g., local environment). It is just a verb phrase and does not help the agent understand the tool's role in the broader workflow.

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 description coverage is 100%, and each parameter has a basic description. The tool description adds no additional meaning beyond the schema, so the baseline 3 applies. It does not clarify relationships between parameters (e.g., tag defaults) or how registry interacts with environmentId.

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 'Pull an image from a registry' clearly identifies the action (pull), resource (image), and source (registry). It is specific enough to distinguish from list/remove/prune but does not explicitly differentiate from the sibling 'arcane_pull_project_images' or clarify that it targets a specific environment.

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?

No guidance is provided on when to use this tool versus alternatives like 'arcane_pull_project_images'. It neither states when to prefer this tool nor mentions any exclusions or prerequisites. The usage context is only implied by the tool name and required environmentId parameter.

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