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

With no annotations, the description carries the full burden. It usefully discloses that the invite stays pending until the recipient signs in and accepts, which is real behavioral context. However, it omits required permission level, duplicate-invite handling, whether an email is dispatched, and whether the call returns an invite object or an ID.

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 sentences, front-loaded with the action and followed by the one non-obvious consequence. No filler, nothing repeated from the schema.

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 two-parameter mutation with no annotations and no output schema, the description explains the lifecycle of the invite but leaves gaps around authorization requirements, error conditions, and what the caller receives back. Adequate but not complete.

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%, and the enum for role with its default is fully documented in the schema, so the baseline of 3 applies. The description adds no semantics beyond the schema — it does not explain the practical difference between owner, admin and member, nor any constraint on which roles an inviter may grant.

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 a human to your organization by email'), which is unambiguous and clearly distinct from file-oriented siblings like drive_share. It does not explicitly name a sibling or contrast with one, 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 — you call this to add a person to the org — but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. needing admin rights) and no pointer to alternatives such as drive_share for resource-level access. The agent must infer the context.

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