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

Annotations carry only openWorldHint, so the description carries nearly the full burden. It does disclose two valuable traits: the mutation changes store access permissions, and it requires owner/admin rights and an account-wide key. It says nothing about reversibility, whether existing store members lose access, or whether the move is atomic — meaningful gaps for an access-control mutation. 3 rather than lower because the access-control side effect and auth requirement are genuinely disclosed.

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?

Two front-loaded sentences: the action first, then the consequence and prerequisite. Both earn their place. Minor deduction for the stray '[#9dde84]' token appended to the description, which is noise rather than content.

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?

No output schema exists, and for a two-parameter mutation the definition covers identity, destination scope, permission requirement, and the key behavioral consequence (access changes). It is close to complete for a call decision; only the post-move effects on existing members and reversibility are unaddressed.

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 100%, so both parameters are already documented in the schema (store_uuid sourced from list_my_stores, workspace_uuid constrained to the same account). The description adds only the framing that the destination is 'one of the account's workspaces', which does not extend beyond the schema text. Baseline 3 applies.

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?

States a specific verb and resource: move a store into one of the account's workspaces, with the scope (agency / Enterprise) called out. It does not distinguish itself from the closely named siblings move_product_to_workspace, move_design_to_workspace, or copy_*_to_workspace, so the agent must infer the store-vs-product boundary from the name alone.

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?

Gives a concrete precondition — account owner/admin plus an account-wide key — and names the plan tiers where workspaces exist, which tells the agent when the call is viable. It stops short of naming alternatives or stating what to do for non-Enterprise accounts / how this differs from a copy operation.

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