cleanup_on_completion

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

With no annotations, the description provides some behavioral traits: returns error if tasks incomplete, force flag overrides, owner-only restriction, and repo_path used for worktree deletion. However, it lacks details on side effects, destructive nature, or exact cleanup behavior, leaving gaps.

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 concise, with a brief summary line followed by a clear bullet-style argument list. Every sentence adds value, and the structure is easy to parse.

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 3 parameters and an output schema, the description covers the main behavior, conditions, and key parameters. However, it omits details about the output format, error types, and whether the operation is reversible, leaving some contextual gaps.

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 explains all three parameters in plain language, adding context beyond the bare schema (which has 0% coverage). Notably, it marks caller_agent_id as required despite schema default null, a critical semantic addition.

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 'Clean up workspace when all tasks are completed,' specifying the condition and action. It also mentions error behavior and force flag, differentiating it from siblings like cleanup_workspace, though lacking explicit sibling comparison.

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 gives clear conditions: use when all tasks are complete, otherwise error unless force=True. It also notes owner-only usage. However, it does not compare with alternative tools like cleanup_workspace or check_all_tasks_completed, leaving usage decision partially ambiguous.

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