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

Annotations cover the safety profile (not read-only, open-world, non-idempotent, non-destructive), and the description adds genuinely new behavior: the invitation email originates from the workspace, names the inviter, owner can never be granted, and an admin cannot grant beyond admin. It omits what happens on a duplicate invite or what permissions the caller needs.

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 tight sentences with the action front-loaded and the privilege constraints compactly stated. Slightly awkward phrasing around "at a role" but no wasted content.

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 simple 2-param mutation with no output schema, the description covers purpose and privilege limits adequately, but leaves gaps on caller authorization, duplicate-invite behavior, and whether an invitation identifier is returned.

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 0% and there are 2 required params, so the description must carry the load. It clarifies that email is the person's address and constrains the role semantics (owner excluded, admin ceiling), but the role values themselves are already in the enum and no format/validation detail for email is given.

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 ("Invite a person to this workspace") plus the mechanism (email address) and the role enumeration. It is clearly distinguishable from siblings like change_a_members_role or remove_a_member, though it never names them explicitly.

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?

The tool's purpose implies when to use it, and the role-cap rules hint at its boundaries, but there is no explicit guidance on when this is preferred over change_a_members_role, nor any stated prerequisites (who may invite whom). Usage has to be inferred.

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