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

Annotations only assert destructiveHint=true, and the description adds real side-effect context beyond that: inviting emails a login unless calls-only, reset emails a new password the user must change, and both should be confirmed with the user. It does not describe what an update overwrites, but the added email/confirmation behavior is genuine value.

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 three actions before the workflow note. The field enumeration is dense but every clause maps to real parameters, so little is wasted.

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 35-parameter mutation tool with no output schema, the description covers the action set, key side effects, and the read-before-write plus confirm-before-invite/reset workflow. Remaining parameter behavior is fully carried by the 100%-covered schema, so nothing critical is missing.

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; the description goes beyond the schema by cross-referencing sibling tools for id sources ('find the ids with get_crm_options kind users', get_users, get_settings), which helps an agent supply valid values.

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 three specific actions on a specific resource: invite a user, edit a profile, reset a password. It is clearly distinguishable from siblings like get_users (read) and remove_user (delete), and the field enumeration makes the scope of 'edit' concrete.

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?

Explicitly gives a prerequisite and workflow: 'Read current values with get_users first; confirm invites and resets with the user,' naming the alternative read tool. It stops short of stating when-not-to-use (e.g., use remove_user for deletion), so it is strong but not fully exhaustive.

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