Manage Container Mount

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

Adds specific details beyond annotations: idempotent returns already_exists or CONFLICT. No contradictions with annotations. Good context on add/remove behavior.

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 focused sentences: first states purpose, second explains idempotency and error cases. No redundancy or fluff.

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 action, idempotency, and error conditions. Lacks explicit statement of return values, but behavior is described. For a mutation tool, mostly complete.

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% with adequate descriptions. Description does not add further parameter meaning beyond schema. Baseline 3 is appropriate.

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 verb ('Add or remove') and resource ('container volume mount'). Distinguishes from sibling tools like manage_container, manage_container_config, etc.

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?

Explains idempotent behavior and conflict scenarios. Could explicitly mention alternatives like list_container_mounts for listing, but the behavior is well described.

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