accept_project_transfer

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

No annotations provided, so description carries full burden. Lists four atomic effects (ownership flip, CI revocation, notifications, advisory), explains secret inheritance and GitHub ownership exclusion. Fully discloses behavior.

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?

Front-loaded with summary sentence, followed by structured list of effects, then clarifications. No redundant text. Each sentence adds necessary information.

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?

Covers preconditions, side effects, and exclusions. Missing return value format, but given the tool is a void-like mutation with no output schema, the description is nearly complete. Slight gap in error scenarios.

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?

Single parameter with 100% schema coverage. Description adds no additional semantic meaning beyond the schema's own parameter description, which already repeats the tool's atomic effects. Baseline 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?

Clear verb ('accept') and resource ('incoming WALLET transfer'). Distinguishes from email transfers via claim_project_transfer and from siblings like cancel_project_transfer, initiate_project_transfer. Includes endpoint and version constraint.

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 when to use: wallet must equal to_wallet. Explicitly excludes email transfers, directing to claim_project_transfer. Provides clear context for correct invocation.

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