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

Annotations only supply destructiveHint=true, leaving the description to explain the effect. It does add real value: 'Reversible by removing them' tells the agent the change can be undone via a sibling operation, and the operation is described as additive membership rather than a destructive overwrite. It does not mention idempotency, duplicate handling, or error behavior, keeping it from a 5.

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 plus the endpoint, all front-loaded with the action and its optionality; nothing is redundant or padded.

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 two-parameter mutation with no output schema, the description covers purpose, optional payload, reversibility and the underlying endpoint. It is close to complete, lacking only failure/duplicate semantics, which is a minor gap.

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 id, roles, permissions and org_code are all documented in the schema itself. The description only restates that roles and permissions are optional, adding no format or constraint detail beyond the schema, so the baseline of 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 ('Add existing users to an organization') plus the optional role/permission payload, which lets an agent place it against list_organization_users and create_organization. It does not explicitly differentiate from the sibling grant_user_role_in_organization, so it falls short of a 5.

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?

'Add existing users' implies the prerequisite that the users must already exist in Kinde, and the mention of optional roles/permissions hints at when to use the richer variant. But there is no explicit when-not guidance or pointer to the granular grant_* siblings, so usage is only implied.

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