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

Annotations only declare it is a non-idempotent, non-destructive write. The description goes well beyond that: real email is sent, existing accounts get the role immediately while others get an invitation, team role is never lowered, SSO-required orgs return 403, and a pre-existing role triggers 409. This is unusually rich side-effect and failure-mode disclosure.

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?

Front-loaded with purpose then side effects then preconditions, and no sentence is filler. It is long and the email-provenance warning is stated twice (once in narrative, once echoed by the schema), which is the only real redundancy.

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?

Complete for a tool with no output schema and partial annotation coverage: it explains the result (role granted now vs. invitation pending acceptance), the permission requirement, the 403/409 outcomes, and the confirmation obligation. An agent has everything needed to call it safely.

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 all three parameters are already documented in-schema, including the role_key-from-listProcessRoles and email-provenance rules. The description restates those same constraints rather than adding new syntax, format, or edge-case semantics, so the baseline 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?

Specific verb+resource+scope: 'Put one person on an automation in one of its process roles,' which cleanly separates it from removeClarityProcessMember, listProcessRoles, and the broader inviteOrgMember sibling. The mechanics of what assigning means are spelled out in the same breath.

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?

Explicit preconditions and alternatives: take role_key from listProcessRoles, managers-and-above permission gate, mandatory user confirmation before calling, and it routes to the People tab when the call is refused. It also states which email addresses are eligible versus which are off-limits.

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