accept_project_transfer

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

With no annotations, the description fully details the atomic operations performed (ownership flip, CI revocation, notifications, advisory stamp) and clarifies important behaviors: secret inheritance with rotation advice, and that GitHub repo ownership is unaffected. This gives the agent a comprehensive understanding of side effects.

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 focused paragraph of about 5 sentences, front-loading the core purpose. Each sentence contributes meaningful detail. Could be slightly more compact, but overall efficient and well-structured.

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 lack of output schema, the description adequately explains what happens during acceptance. It covers key outcomes and behaviors. However, it does not mention error conditions or the state of the transfer post-acceptance (e.g., removal from incoming list). Still largely complete for a single-parameter tool.

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 schema covers the single parameter with a description that largely mirrors the main description. Since schema coverage is 100%, baseline is 3. The description adds some extra context (atomic effects) but does not significantly enhance what the schema already provides.

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 tool's action ('Accept an incoming WALLET transfer'), specifies the version requirement (v1.93+), and immediately distinguishes it from email transfers which use 'claim_project_transfer'. It also enumerates specific atomic effects, leaving no ambiguity about what the tool does.

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 specifies a key precondition ('Your wallet must equal the transfer's to_wallet') and explicitly states when not to use this tool ('Email transfers complete via claim_project_transfer, not this tool'). However, it could more directly state that this is solely for wallet-to-wallet transfers, though this is implied.

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