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

Annotations already declare a non-readonly, non-idempotent, non-destructive, open-world mutation. The description adds useful context about email-based invitation and optional team placement, but it does not disclose permission requirements, duplicate-invite behavior, invitation expiry, or role implications.

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 front-loaded sentence with no wasted words. It states the action, channel, target resource, and optional team placement efficiently.

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?

The annotations cover the safety profile and the schema exposes required fields and role enum, so the description is minimally sufficient for invocation. It still leaves gaps around role meaning, permissions, duplicate invitations, and invitation lifecycle, which matter for a mutation tool with low schema description coverage.

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 only 25%, so the description must add meaning. It clarifies email invitation and optional team assignment, which helps with email, orgId, and teamId, but it does not explain the role parameter or its MEMBER/ADMIN/OWNER semantics and default.

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 to an organization by email. It also notes the optional team assignment. It does not distinguish this from siblings such as invite_member or add_team_to_organization, so it stops short of a 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?

Usage is implied through 'optionally straight into one of its teams,' which clarifies when teamId may be used. However, there is no explicit guidance on when to choose this over invite_member, add_team_to_organization, or what prerequisites are needed.

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