build_image

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

Discloses that build context is the folder containing the Dockerfile, that COPY/ADD of other files works normally, and that Windows and Git Bash style paths are accepted. No annotations to contradict.

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 paragraphs plus Args list, each sentence adds value. Could be slightly more concise but well-structured and front-loaded.

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?

Covers purpose, parameters, and key behavioral trait, but lacks explanation of output/return value and potential errors. With output schema not shown, some gap remains for a build 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 descriptions are absent (0% coverage); description adds full meaning: image_tag example and dockerfile_path explanation including path styles, fully compensating for lack of schema descriptions.

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?

Description clearly states 'Builds a Docker image from a Dockerfile' with specific verb and resource. Distinguishes from sibling tools like push_image, run_container, delete_image.

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?

Provides context such as build context behavior and path formats, but does not explicitly state when to use versus alternatives or when not to use.

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