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

With readOnlyHint=false, the description correctly implies a mutation, but it only discloses one behavioral aspect (not returning token material). It does not mention side effects like sending an email or requiring confirmation (which the title hints at), nor does it provide context about idempotency or error handling. Given the sparse annotations, the description carries the burden and fails to adequately disclose behavior.

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 a single, concise sentence with no filler words. It front-loads the action and includes a relevant behavioral note. However, it may be slightly too terse given the complexity of the tool, but as far as conciseness goes, it is efficient.

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 tool with 8 parameters, 3 required, no schema descriptions, and no output schema, this description is severely incomplete. It does not explain required inputs, the role enum, expiration behavior, idempotency, or what happens after creation. An agent cannot confidently invoke this tool correctly based on the provided information.

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?

The input schema has 8 parameters, all with zero description coverage, and the description mentions none of them. It does not clarify the meaning of department_id, email, role, idempotency_key, expires_in_hours, etc. The description provides no compensation for the missing schema descriptions, leaving the agent to guess parameter semantics.

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 clearly states the action ('Create'), the resource ('invitation'), and the scope ('Department-scoped'). It also adds a specific detail about behavior ('without returning token material'), which makes the purpose unambiguous and distinguishes it from other invitation-related tools like listing.

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 description does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or other tools (e.g., the sibling list tool). The intended usage is only implied by the name and the word 'Create'.

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