check_engine_image

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

With no annotations, the description fully discloses behavior: no image layers downloaded, uses docker manifest inspect, returns up_to_date+recommend_pull, auto_pull runs docker pull on stale/missing, and version evolution independence.

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?

Description is concise with 4-5 well-structured sentences, front-loaded with core purpose, no superfluous information.

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 no output schema, the description mentions return fields (up_to_date, recommend_pull) but lacks detailed format. Siblings are referenced indirectly. Still adequate for a simple check 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?

Schema coverage is 100%, and description adds meaning beyond schema by explaining default values and auto_pull behavior (runs pull when stale or missing).

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 the tool checks if the local Docker image is up to date with the registry, using specific verbs and resource. It distinguishes itself from sibling tool pull_engine_image by offering both check and optional pull.

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 when to use the tool (to check and optionally pull) and notes independence from MCP server version. It implies alternative pull_engine_image, but could be more explicit about not needing to check before pulling.

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