accept_project_transfer

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

With no annotations, the description details the atomic effects: flips ownership, revokes CI bindings, enqueues notifications, and stamps advisory. It also mentions secret inheritance and rotation advisory. This provides good behavioral insight, though it lacks mention of authentication or rate limits.

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 no redundant information. It is front-loaded with the main purpose, then precondition, then a clear list of atomic effects, and ends with important notes. Every sentence serves a purpose.

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 (atomic operations) and single parameter, the description is comprehensive. It does not specify return value or error conditions, which could be improved, but the core behavior and constraints are well-covered.

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 only parameter transfer_id has 100% schema description coverage. The main description adds value by explaining the wallet precondition and atomic effects, which are not fully covered in the schema. This provides necessary context for correct usage.

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 'Accept an incoming project transfer (v1.59+)', specifying the verb 'accept' and resource 'incoming project transfer'. It distinguishes from siblings like initiate_project_transfer, cancel_project_transfer, and preview_project_transfer by focusing on the accept action.

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 explicitly requires 'Your wallet must equal the transfer's to_wallet', providing a clear precondition. It also clarifies that GitHub repo ownership is not part of the transfer, offering a limitation. However, it does not explicitly state when not to use or compare with other transfer tools.

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