Add Organization Member

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

It adds substantial behavioral context beyond the annotations: the invitation is pending, the user joins with the member role only after accepting, an external email is sent, and admin credentials are required. The safety warning to confirm the exact organization and email before calling is especially valuable for a mutating invitation tool.

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 front-loaded with Purpose and organized into Purpose, Returns, Behavior, Auth, and Safety sections. It is somewhat long, but each section adds actionable information rather than repeating structured fields.

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?

With no output schema, the description explicitly covers return values, pending-invitation behavior, role assignment, authentication requirements, and safety constraints. Nothing material is missing for an agent deciding whether and how to invoke this tool.

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% and both parameters already have descriptions, so the description need not carry the parameter burden. It adds no syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: starting to add a member by sending an invitation to an email address. It clearly distinguishes this from list-organization-members and update-organization-member by explaining the pending-invitation lifecycle and post-acceptance promotion path.

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?

It gives clear usage context, including that the person will not appear in list-organization-members until acceptance and that update-organization-member should be used afterward to promote them. It stops short of naming explicit when-not-to-use conditions or all alternative member-management tools.

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