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

Goes well beyond annotations by disclosing that an email with a join link is sent, specifying authorization requirements, and describing the QUOTA_EXCEEDED error path with the next upgrade_plan action. This adds useful operational context for a non-read-only, 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?

Four short sentences, front-loaded with the core action and side effect, then prerequisites and error behavior. There is little waste and the important constraints are easy to scan.

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?

Given a simple three-parameter mutation with no output schema, the description covers side effects, permissions, plan requirements, and the quota error path. The main remaining gap is role semantics: the description never explains what role the inviter can assign or how to choose MEMBER versus ADMIN versus OWNER.

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 low at 33%, with only teamId documented in the schema. The description mentions email and team context but does not explain the role parameter, its MEMBER/ADMIN/OWNER enum values, or the MEMBER default, so it does not compensate for the low 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 and resource: invite someone to a team by email. It is clearly distinguishable from sibling tools such as invite_to_organization and list_team_invitations, which concern organization-level or listing operations.

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?

Gives clear prerequisites (owners/admins only, Team plan required) and names upgrade_plan as the alternative when quota is exceeded. It also says to ask the user rather than choose for them, though it does not explicitly address when to use invite_to_organization instead.

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