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: ownership flip, CI binding revocation, notification enqueuing, and secrets_rotation_advised stamp. It also mentions secret inheritance and GitHub ownership exclusion, providing comprehensive behavioral context.

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 moderately sized but front-loaded with key information. It is well-structured with purpose, prerequisites, atomic effects, caveats, and API endpoint, each sentence adding value without redundancy.

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?

Despite a single parameter, no output schema, and missing annotations, the description covers all critical aspects: prerequisites, atomic behavior, post-transfer advisories, and exclusions, making it fully complete for the tool's complexity.

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 coverage is 100% with the parameter description repeating the tool description. The description adds no additional parameter semantics beyond what the schema already provides, so baseline score of 3 is appropriate.

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 accepts an incoming WALLET transfer, specifies the version requirement (v1.93+), and distinguishes from sibling tools like claim_project_transfer and cancel_project_transfer, providing a specific verb and resource.

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 states the prerequisite that the wallet must equal the transfer's to_wallet, and clarifies that email transfers use claim_project_transfer instead, providing clear when-to-use and when-not-to-use guidance.

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