Transfer work

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hints at 'versioned' and 'evidence-bearing handoff' but does not explain what versioning entails, whether actions are reversible, what state transitions occur, or what happens on failure. The description is too sparse to convey the operational impact of this mutation tool.

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 a single, front-loaded sentence that efficiently conveys the core action set and concept. It contains no filler and gets to the point immediately. For a tool with 19 parameters, it is appropriately terse, though it could arguably benefit from more structure to improve scannability.

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 the tool's complexity (19 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain the versioning mechanism, the required fields for each action, the nature of an 'evidence-bearing handoff', or how these actions fit into the broader workflow with siblings. An agent would need to infer too much to use it correctly and safely.

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 description coverage is 79%, which is high, so the baseline is 3. The tool description adds no parameter-specific details beyond listing the action enum values, which are already present in the schema. Since the schema already documents parameters like task_id, action, expected_version, and to_agent_id, the description's lack of parameter elaboration does not significantly hinder understanding.

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 states a clear verb ('Apply') and a specific resource ('versioned ownership action') and enumerates all seven allowed actions, making the tool's purpose unambiguous. It does not explicitly contrast with sibling tools, but the action list clearly distinguishes it from start_work, update_work, and finish_work, so the purpose is well-defined.

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?

There is no guidance on when to use this tool versus its siblings. The description does not mention that this is for transferring ownership between agents, nor does it reference start_work, update_work, or finish_work, or any conditions that would make this tool the right choice. An agent is left to infer usage context.

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