initiate_project_transfer

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

With no annotations provided, the description carries the full burden and does an excellent job: it discloses that transfers create a pending row with 72h expiry, freeze owner-side mutations, do not refund tier lease, and do not transfer GitHub ownership. It also specifies that for org transfers completion is immediate.

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 fairly long but well-structured: first sentence captures the main action, then recipient options, then conditions and behavioral details. Every sentence adds information, though a slight tightening could improve front-loading for quick scanning. No 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?

Given the complexity (8 parameters, no output schema, no annotations), the description is very complete. It explains the full lifecycle (pending, completion, freezing, expiry, billing policy, no refund, no GitHub transfer), the API endpoint, and all parameter constraints. There are no obvious gaps.

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 already covers 100% of parameters, but the description adds significant value by explaining that exactly one of to_wallet/to_email/to_org_id must be provided, the conditions for to_org_id (same-actor, owner of both orgs), and which parameters are rail-specific (billing_policy, kysigned_record_id for wallet; retain_collaborator_role for email). It also clarifies the optional nature of message.

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 main action 'Initiate a project transfer' and details three distinct recipient types (wallet, email, org) with specific completion tools. It distinguishes from siblings like accept_project_transfer and cancel_project_transfer by noting they are completions.

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 explains when to use each recipient option (exactly one) and conditions such as owning the project and being an active owner of orgs. It mentions that wallet/email transfers create pending rows with 72h expiry and freeze mutations. It could be more explicit about when not to use the tool (e.g., if the project is already in transfer), but the context is clear.

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