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

With no annotations, the description carries full responsibility. It discloses role validation constraints and the fact that the invitee receives an email with an acceptance link. However, it omits behavioral details such as what happens on failure (e.g., duplicate invite, invalid email), rate limits, or whether the invitation creates a pending user record.

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 extremely concise: three sentences that deliver the core action, constraints, and outcome. Every sentence earns its place, with the main action and context front-loaded. No wasteful or redundant 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?

Given the tool's simplicity (3 parameters, no output schema, no nested objects), the description covers the essential context: organization binding, role constraints, and the email notification. However, it lacks information about the return value (e.g., success indicator, invite ID) which would be helpful for completeness.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by clarifying that the organization is implicitly determined by context, that role validation checks against the caller's privilege, and that the idempotency_key can be used for safe retries. This enriches the parameter understanding.

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 clearly states the action ('invite a person') and the resource ('to join your organization by email at a chosen role'). It uses specific verbs and nouns, and differentiates from sibling tools like cancel_invite and resend_invite by focusing on the initial invitation action.

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 provides explicit context on usage: the organization is fixed (do not pass an id) and role constraints based on the caller's privilege. It does not explicitly list when not to use or mention alternatives, but the context is clear enough for an agent to decide when to invoke this tool.

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