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

Annotations already declare readOnly=false, idempotent=false, openWorld=true and destructive=false, so safety profile is covered. The description adds genuinely new behavioral context: seat cost ($5/month, prorated in the joining month). However it omits that an email is actually dispatched and that permissions/admin scope may matter.

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?

A single front-loaded sentence with the cost caveat neatly parenthesized; nothing is wasted. It's efficient but the brevity contributes to the missing context elsewhere.

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 three-parameter, non-idempotent, open-world mutation with no output schema and low schema coverage, the description should say what happens (invite sent, seat billed) and who can do it. It covers cost but leaves the operational and permission picture thin.

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 33% – the email, role, and default-org semantics are largely undocumented in the schema, and the description adds nothing about parameters. The role enum is self-documenting, but nothing explains the default-org fallback or valid email constraints beyond the pattern.

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+resource ('Invite someone by email') that cleanly separates it from neighbors like cloud_team_resend or cloud_invites_accept. It never explicitly names those siblings as alternatives, 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?

The description tells the agent that each invite costs money, which hints the agent should intend to invite, but it gives no when-to-use vs when-not-to-use guidance relative to cloud_team_resend, cloud_invites_get, or cloud_invites_accept. No prerequisites (e.g. admin permission) are stated.

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