cancel_project_transfer

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

With no annotations, the description carries the full burden. It discloses that cancellation is only possible for pending transfers, that only the involved parties can cancel, and that already-processed transfers return an error. It also specifies the HTTP method and endpoint. Missing details like irreversibility or notification of parties, but adequate for a simple action.

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?

Three concise sentences with no fluff. The most critical information (action, version, eligibility, endpoint, error cases) is front-loaded and efficiently stated.

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 tool with 2 parameters (1 required) and no output schema, the description covers the essential behavioral aspects: what it does, who can do it, and when it fails. It could mention that the cancellation is irreversible or that both parties are notified, but overall it is complete enough for an agent to invoke correctly.

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%, so baseline is 3. The description adds minimal extra meaning beyond the schema's parameter descriptions (e.g., transfer_id description already states who must be the parties). The description does not further elaborate on the 'reason' parameter. Schema alone is sufficient.

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?

Clearly states the action (cancel a pending project transfer), specifies version requirement (v1.59+), identifies who can perform it (either party), and provides the exact API endpoint (POST /agent/v1/transfers/:transfer_id/cancel). This distinguishes it from sibling tools like initiate_project_transfer and accept_project_transfer.

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?

Explicitly states that either party may cancel and describes error condition (already-accepted/cancelled/expired return 409). While it does not explicitly mention when not to use or compare to alternatives, the context of pending transfers and the API endpoint provides clear guidance. A slight improvement would be to note that cancellation is only possible for pending transfers.

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