Transfer profiles to another user

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

The description discloses a significant backend quirk: false success when the recipient email does not exist. It also adds the permission requirement. While destructiveHint is already in annotations, the quirk adds valuable behavioral context beyond the structured data.

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?

Three focused sentences: one for the action, one for the prerequisite, and one for the critical quirk. No filler, and the most important operational warning is front-loaded.

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 permissions, the false-success quirk, and the transfer action. It does not describe the return value, but there is no output schema. Missing details about proxy movement behavior are already in the schema, so overall it is reasonably complete.

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?

Schema coverage is 67%, so parameters are mostly described in the schema. The tool description mentions 'by email' which aligns with the username parameter, but it does not add new meaning to ids or withProxy beyond their existing schema descriptions.

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 verb 'Move', the resource 'profiles', and the target 'another Dolphin{anty} account by email'. This distinguishes it from sibling tools like delete_profiles (delete) and share_profile_access (share, not transfer).

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?

It states a prerequisite: 'You must own the profiles or hold the `share` permission.' It does not explicitly mention alternatives or when not to use, but the purpose is clear enough that it is likely the correct tool for transferring ownership.

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