buildx_remove

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

Annotations already indicate destructiveness (destructiveHint=true). The description adds behavioral details: parameters like 'force' (forced removal), 'keep_state', 'keep_daemon', and mutual exclusivity of 'name' and 'all_inactive'. This goes beyond the schema and annotations, though it could mention what happens to associated resources.

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 brief yet comprehensive. The main purpose is front-loaded, and the parameter documentation is structured as a clear list. Every sentence adds value without 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?

The description covers all parameters and specifies the return value (a dict with status fields), which is helpful given no output schema. It does not cover edge cases like handling missing builders, but the 'force' flag addresses common concerns. Overall, it is sufficiently complete for a removal 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?

The input schema has no property descriptions (0% coverage). The description compensates fully by explaining each parameter's purpose, including the mutual exclusivity constraint and the effect of boolean flags. This provides critical meaning beyond the schema's types and defaults.

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 action: 'Remove a builder instance.' It uses a specific verb and resource, distinguishing it from sibling tools like buildx_create or buildx_list. However, it does not explicitly contrast with other removal tools such as buildx_prune.

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 provides no guidance on when to use this tool versus alternatives. Given the extensive list of sibling tools, including buildx_prune and container_remove, the agent needs contextual clues to choose correctly, which are absent.

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