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

Annotations are neutral (not readOnly, etc.), but description adds key behavior: auto-creation of non-existent users and full role reset on move_from_other_groups=true. This provides valuable context beyond annotations.

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 sentences, concise and front-loaded with purpose, followed by behavioral clarifications. No wasted words.

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?

Mutation tool with no output schema; description covers creation, move behavior, and parameter effects. Lacks permissions or return value info but sufficient for intended use.

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 100% with adequate descriptions; description adds extra detail for move_from_other_groups but does not significantly enhance understanding of other parameters.

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?

Description states specific action: adding a user to a team group by email, and distinguishes from siblings like add_user_to_portal_group. It also covers user creation and move_from_other_groups behavior, making the purpose very clear.

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?

Implied usage for adding users to team groups; no explicit when-not or alternative tools, but context is clear from sibling names and description.

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