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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds useful behavioral context that approvals may be required and that business workflow approvals always apply, though it does not detail permission requirements or duplicate-membership behavior.

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, front-loaded with the core action. The approval sentence is relevant but slightly vague; overall there is little waste.

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?

This is a mutation tool with a nested input object and zero schema description coverage, but the description omits parameter details and does not explain permission or duplicate-handling behavior. Output schema and annotations cover some context, but significant gaps remain for correct invocation.

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 0%, and the nested data object includes role, team, addedAt, and userId without any description-level explanation. The first sentence only loosely implies siteId and userId, leaving role, team, and addedAt unexplained.

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 states a specific verb and resource: assign an existing organization user to a site team. It distinguishes this from invite_team_member by specifying an existing user, and from add_project_team_member by specifying a site team.

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 action is clear enough to imply when the tool should be used, but it does not explicitly compare against alternatives like add_project_team_member or invite_team_member. The approval note provides context but not selection guidance.

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