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

Annotations already indicate non-read-only, non-idempotent, non-destructive, but the description adds critical behavioral context: the invitee becomes a member only on first sign-in, appears in list_invites until then, and the operation returns a pending object. It also flags that the invite alone grants no data access, which is a non-obvious behavior. No contradiction with annotations.

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?

The description is moderately sized but well-organized, front-loading the core purpose and admin constraint before diving into usage details. It includes the return shape and cross-references, which adds length but each sentence contributes value. It could be trimmed slightly, but it remains focused and readable.

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?

Despite no output schema, the description explicitly lists the return object fields, covers the admin restriction, the sign-in timing, the distinction from list_invites, and the mandatory follow-up with grant_env. It fully equips an agent to decide when to invoke and what to expect, with no critical gaps for a 3-parameter tool.

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 baseline is 3, but the description enriches every parameter: org explains automatic resolution and error behavior when ambiguous, role explains default and admin capabilities, email explains the invitation lifecycle and where the invitee appears. This far exceeds simple schema repetition, providing actionable guidance for correct invocation.

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 states a specific verb (Invite), resource (a human to the organization by email), and constraints (admin only, joins at given role on sign-in). It clearly differentiates from sibling tools like revoke_invite and list_invites by explaining the lifecycle and the follow-up grant_env step. The purpose is unambiguous and action-oriented.

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 explicitly states the admin-only prerequisite and the intended use case ('hand a project off to a person'). It also clarifies what an invite does NOT do (conveys no read ability) and directs to grant_env for decryption, effectively telling the agent when not to rely on this alone. Mention of revoke_invite as the cancellation mechanism further guides usage.

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