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

Beyond the sparse annotations (openWorldHint false, destructiveHint false), the description discloses it is a 'cross-user mutation' and that the server enforces 'reviewer/admin/service role'. This adds meaningful behavioral context about the mutation nature and permission requirements, which is not evident from annotations alone. No contradiction.

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 two concise sentences with the main action in the first sentence and important context in the second. There is no filler or redundancy; every word earns its place.

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 an output schema and minimal annotations, the description sufficiently covers purpose, context, required role, and the cross-user nature. The output schema likely handles return value details, so the description is complete enough for an agent to know when and how to invoke this tool.

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 only provides 'UUID value wrapper' descriptions, so the names carry the meaning. The description adds semantic context by explaining that fromUserId is the hardcoded demo user, toUserId is the real user, and sessionId identifies the demo session. This helps the agent map parameters to their roles, though not exhaustively.

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 uses a specific verb ('reassigns') and resource ('formations created during a demo session') and places it in a clear context ('to a newly-signed-up real user'). This distinguishes it from the many sibling formation_* tools, which have different purposes. The action and scope are unambiguous.

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 gives a clear context for when this tool is appropriate (claiming demo formations for a newly signed-up user) and notes server-enforced roles. It does not explicitly list alternative tools or state 'don't use for X', but the specificity effectively implies the intended use case.

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