cancel_project_transfer

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

With no annotations, the description carries full burden. It discloses authorization conditions, error handling for already-processed transfers, the HTTP endpoint, and version requirement. It does not mention idempotency or side effects beyond the error, which is acceptable for a cancellation 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 four sentences with no fluff. It front-loads the core purpose and version, then provides authorization, error info, and endpoint. Every sentence earns its place.

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?

For a simple cancellation tool with two parameters and no output schema, the description covers core functionality, authorization, and errors. However, it does not specify the success response (e.g., what a successful cancellation returns), leaving a minor gap. Adequate but not 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%, but the description adds meaning by noting the transfer_id is 'Kind-agnostic' and that the reason is 'Optional free-text cancellation reason recorded on the audit row.' It also reiterates authorization context for transfer_id, adding value beyond the schema.

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 'Cancel a pending project transfer of any kind' and includes version requirement v1.93+. It distinguishes from siblings like accept_project_transfer, initiate_project_transfer, etc., by focusing on cancellation of pending transfers.

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 context on when to use (pending transfers) and conditions leading to 409 TRANSFER_ALREADY_PROCESSED. It also outlines authorization requirements. However, it does not explicitly exclude when not to use it or contrast with alternative sibling tools like accept_project_transfer.

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