post_workspaces__wid__profiles_transfer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Transfer profile' implies a mutation operation that moves profiles between instances or users, but it doesn't disclose whether this requires specific permissions, whether the transfer is reversible, what happens to the source profile after transfer, or any rate limits. The description adds minimal behavioral context beyond the basic operation name.

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 extremely concise at just two words, which could be appropriate if it were more informative. However, this brevity comes at the cost of clarity. While there's no wasted language, the description is under-specified rather than efficiently informative.

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?

For a mutation tool with 3 required parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what a 'profile' is in this system, what the transfer operation actually does, what the expected outcome is, or any error conditions. The agent would need to infer too much from the minimal description.

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 description coverage is 67% (2 of 3 parameters have descriptions), so the baseline is 3. The description 'Transfer profile' adds no meaningful parameter semantics beyond what the schema already provides. It doesn't explain the relationship between 'wid', 'toEmail', and 'instanceIds', or provide context about what constitutes valid instance IDs or email addresses.

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 'Transfer profile' is a tautology that restates the tool name without adding meaningful context. It doesn't specify what 'profile' means in this context, what resource is being transferred, or what the transfer operation entails. While it includes a verb ('Transfer') and a resource ('profile'), it lacks the specificity needed to distinguish this from sibling tools like 'post_profile_clone_multi' or 'post_deleted_profiles_restore'.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions. Given the sibling tools include various profile-related operations (clone, restore, delete), the absence of usage guidelines leaves the agent guessing about when this specific transfer operation is appropriate.

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