build_fetch

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

Explicitly states it is non-mutating on the build host and only affects local disk, which is good behavioral disclosure. Missing deeper details like permissions or error states.

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 efficient sentences convey purpose, specifics, and behavioral note with no redundant 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?

Covers key aspects: what is copied, destination, mutability. An output schema exists to describe returns. Slightly lacking on whether tag must pre-exist.

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?

The description uses 'tag' in the path, providing context that it is a folder name, but does not explain valid values or format. With 0% schema coverage, more would be beneficial.

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 the tool copies build artifacts (kernel, userspace image, metadata) to a specific path on Mac, distinguishing it from sibling tools like build_start or build_deploy.

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 explicit guidance on when to use this tool versus alternatives. The action is implied but lacks context like prerequisites or typical workflow placement.

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