Resend user invite

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description adds nothing beyond restating the title. It omits the practically important behavior for a resend (whether the prior invite/link is invalidated, regeneration of the token, and any rate limiting), which matters precisely because idempotentHint=false hints at side effects.

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?

A single short sentence with the action front-loaded and zero filler. It is efficient, though the brevity borders on under-specification rather than tight editing.

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 one-parameter, non-destructive-by-annotation tool with full schema coverage and no output schema, this is minimally sufficient. However, since the operation sends an email and is flagged non-idempotent, some note on re-send consequences or failure modes would round it out.

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 100% with a single documented parameter (inviteId), so the schema already carries the semantics. The description adds no format, sourcing, or constraints beyond it, which is the expected baseline for full coverage.

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 ('Resend') and resource ('user invite email'), which is clear and matches the title. It does not distinguish itself from the near-identical sibling tailscale_resend_device_invite, but the resource noun 'user' does most of the work.

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?

Usage is only implied: an agent can infer it should be called when an invitee needs a new invite email, but the description gives no explicit when-to-use, when-not-to-use, or alternative (e.g., delete + recreate invite, or the device-invite variant).

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