Invite someone by email

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds the important detail that the write is gated behind confirm: true and that there is no server-side dry run, which an agent cannot infer from the annotations. It still says nothing about required permissions or error behaviour for an open-world mutation.

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 short, front-loaded clauses with no wasted wording; the write-safety caveat comes before any subordinate detail. It is arguably too terse rather than padded, but nothing is redundant.

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 should say more about what comes back (preview payload vs. created invite) and about authorization requirements for an open-world write. For a nested-body mutation tool, the current two sentences are minimal but not wrong.

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%, and the confirm and idempotencyKey parameters are already documented in the schema, so the description's mention of confirm largely restates structured data. The nested body fields (role enum values, clientId, permissions) are unexplained in both places, leaving the gap unfilled.

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 gives a specific verb and resource ("Invite someone by email") plus the underlying endpoint POST /v1/invites, so the action is unambiguous. It does not name the neighbouring invites_preview or invites_revoke tools, so sibling differentiation is only implied by the verb.

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 clearly states the precondition for execution (confirm: true) and that otherwise nothing is sent, which is real usage guidance. It never points to invites_preview as the way to inspect an invite or to invites_list for existing invites, so the when-to-use-this-vs-alternatives guidance is inferred rather than explicit.

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