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

Annotations only declare it is a non-read, non-destructive, non-idempotent mutation; the description adds substantially more: no notification email is sent, the response carries a text sign-in link to relay, joining happens on first sign-in via Google or primary GitHub email, and pre-existing DenkOps users are added immediately. That is exactly the non-obvious behavior an agent needs before calling it.

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?

Four tight sentences, front-loaded with the action and the critical 'no email is sent' caveat. Dense but nearly every clause carries operational information; only the parenthetical identity detail could be trimmed slightly.

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?

With no output schema, the description usefully explains what the result contains (a short text with the sign-in link). It covers prerequisites and the invite lifecycle well, though it is silent on invite expiry and on how a github_login-only invite resolves to a user.

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 0%, so the description must carry parameter meaning. It does well on the email parameter (it must match the invitee's sign-in identity) and notes GitHub username as an alternative, but it never addresses the role enum values, the 'member' default, or whether email and github_login are mutually exclusive despite zero required parameters.

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?

The description opens with a precise verb and resource ('Invite someone to the workspace') plus the two identifying methods (email or GitHub username) and the role argument. It is clearly distinguishable from siblings like remove_member, cancel_invite, and set_member_role without opening a schema.

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?

It states a hard precondition ('Workspace owners only') and clarifies the unusual invite semantics (no email is sent; the caller must pass on the sign-in link). It stops short of naming alternatives such as cancel_invite or set_member_role, and does not say when to prefer email over github_login.

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