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

With no annotations, the description carries the full behavioral burden, and it discloses only the auth mode ('User session only'). It does not say that an email invitation is dispatched, whether the call is idempotent for an existing member, what happens if the role is invalid, or whether the invite expires — all material for a mutation tool.

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 compact clauses, front-loaded with the action and the key enum, with no filler. The terseness borders on under-specification, but nothing 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 an unannotated, non-idempotent-looking invite mutation with no output schema, the definition omits side effects, error conditions, and permission requirements. An agent could call it, but cannot predict the result or failure modes from the text.

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 67%, so the schema already documents workspace_id as a notebook UUID and role with its allowed values and default. The description's '(viewer|editor|owner)' merely repeats the role enum and adds nothing about email semantics or role scope.

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 member by email') plus the role vocabulary, which is enough to separate it from link-sharing siblings like share_create_link. It does not explicitly name or contrast an alternative, so it stops short of 5.

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?

'User session only' implicitly tells the agent this call is unavailable to API-key/service-account contexts, which is a genuine usage constraint. However, there is no guidance on when to invite a member versus creating a share link, nor on prerequisites such as whether the email must belong to an existing account.

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