pull_image

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

No annotations are provided, so the description carries the full behavioral burden and discloses nothing: not that it downloads/changes local state, not whether it blocks, not whether auth or a registry is required, not what happens on name conflicts. A two-word restatement of the name provides zero behavioral context.

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 under-specification, not conciseness. There is nothing to be front-loaded because no information is present.

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 an operation that mutates local image state, with no annotations, no output schema, and an undocumented required parameter, the definition is completely inadequate for correct invocation.

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 0%, and the description never mentions the single required parameter "name". It does not say whether name should include a tag, a registry prefix, or a digest — all of which matter for a pull operation.

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?

"Pull image" restates the tool name pull_image almost verbatim, which the rubric classifies as tautology. The verb+resource is technically present, but it gives no distinguishing detail versus siblings like push_image, load_image, build_image, or search_images.

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 indication of when to use this tool versus alternatives such as search_images (find an image) or load_image (import from an archive). No prerequisites, no registry context, nothing to route the agent.

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