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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: the permission model and the org-membership requirement. It does not address what happens on re-adding an existing member or whether an invitation is dispatched.

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?

Four tight sentences: the operation first, then role semantics, then authorization, then the org precondition. No filler and nothing redundant with the schema.

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?

With no output schema, return values need not be explained, and annotations cover safety. For a mutation tool the description supplies permissions and preconditions, but leaves open whether the person must already have an account or is invited, which matters given the sibling invite_member.

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%, so the baseline is 3, but the description goes further by defining the semantics of each role value (team_admin manages the team, editor edits flows, viewer only opens flows) rather than just listing the enum. team_id and email are left to the schema, which is acceptable given its descriptions.

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 ('add'), a specific resource ('one person to a team') and the scoping attribute ('with a role'), which cleanly separates it from flow-level siblings like add_to_flow and add_collaborator. An agent can identify the operation without opening the schema.

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?

It states the authorization prerequisites explicitly ('Only a team admin, the team owner, or an organization owner or admin can do this') and the org-team precondition. It gives clear when-you-may-use context but never names an alternative sibling (e.g. invite_member for someone not yet in the org), so there is no explicit when-not routing.

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