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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description's added value is the word 'invite', which implies an outbound email/membership side effect, but it never says an email is dispatched, that a role is granted, or that role='admin' is privileged — all relevant given destructiveHint=true.

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 short clauses, front-loaded and waste-free, though 'Add a User' largely restates the tool name and title before the more informative 'Invite' clause.

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?

An output schema exists so return values need no explanation, and annotations carry the safety signal. However, for a mutation that grants account access and is flagged destructive, the description omits permission requirements, invitation/email behavior, and role implications, leaving meaningful gaps.

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% and each parameter (url, role enum, email, workspace_id) is documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema — nothing about what each role grants or how workspace_id scoping affects the invitation.

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 plus the key nuance that this is an *invitation* ('Invite a new user to your account'), which separates it from plain record creation. It does not explicitly distinguish itself from siblings like add_contacts or update_user, so an agent must infer the boundary.

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?

There is no when-to-use guidance, no prerequisite (e.g. admin permission), and no mention of alternatives such as update_user for existing members or get_all_users to check for duplicates. The agent is left to infer all routing decisions.

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