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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true), the description discloses the 1–20 batch limit, a concurrency cap of four simultaneous invite requests, and that accepted invitations are queued for delivery through SYNCDATE Mailer. That is substantive operational context an agent could not infer from the annotations. It still says nothing about partial failure or permission requirements.

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?

Three short, front-loaded sentences with no filler; the action and batch constraint lead, with concurrency and delivery details trailing. Every sentence adds information.

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 mutation with no output schema and only partial annotation coverage, the description covers batch size, concurrency, and delivery path but omits what happens with duplicate or already-invited addresses, whether failures are partial, and what privileges are required. Adequate but with clear gaps.

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 0%, so the description must carry the load. It clarifies that emails are email addresses and states the 1–20 bound (already encoded as minItems/maxItems in the schema), but organizationId is never explained — no indication that it is the target team's UUID. One of two parameters remains semantically undocumented.

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 opens with a specific verb+resource: "Invite 1–20 email addresses to the Team per call." An agent immediately knows this adds people to a team, and the per-call batch bound is stated. It does not differentiate itself from close siblings like update_team_invite or update_team_member, which keeps it out of 5 territory.

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?

There is no when-to-use guidance and no named alternative among the many team-related siblings (update_team_invite, request_team_auto_join_domain, update_team_member). The batch and concurrency limits are invocation constraints, not routing advice, so the agent gets no help deciding between this tool and its neighbors.

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