check_engine_image

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

The description discloses the technical mechanism (docker manifest inspect without layers), the return flags, and the optional pull behavior. The note about being independent of MCP server version adds valuable context. Since no annotations are provided, the description carries full burden and does a good job, though it could mention potential side effects like network requirements or that auto_pull modifies local Docker state.

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 compact (two short paragraphs) with all essential information front-loaded. Every sentence adds value: the core purpose, the technical detail, the return values, the optional pull, and the clarifying note. No filler or 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 tool's moderate complexity (2 params, no output schema, no annotations), the description covers the key aspects: what it does, how it works, what it returns, and the autopull option. It is largely complete, but could mention error handling or Docker daemon requirements for full completeness.

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?

Both parameters (image and auto_pull) are fully described in the schema, and the description adds default values and behavioral context (e.g., default image and what auto_pull does when true). This exceeds the baseline of 3, as it adds meaningful guidance beyond the schema alone.

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 that the tool checks if the local Docker image is up-to-date vs. the registry, with optional auto-pull. It distinguishes itself from sibling tools like pull_engine_image by offering a combined check+optionally pull. The verb 'check' and resource 'engine image' are specific and unambiguous.

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 explains the primary use case: check image freshness before running workflows. The optional auto_pull behavior is clearly described, and the note about version independence helps avoid confusion. However, it does not explicitly state when not to use it (e.g., if you only want to pull without check, use pull_engine_image) or mention prerequisites like Docker availability.

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