Bulk Invite Project Members

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

The description discloses a key behavioral trait beyond the annotations: it sends real invitation emails for entries that don't match existing users, implying that existing users are added directly without email. This adds valuable context beyond readOnlyHint=false and openWorldHint=true, which alone do not specify the email side effect.

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 sentences, front-loaded with the primary action and immediately adding the critical email caveat. Every word earns its place; there is no filler or redundancy.

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 bulk operation with nested objects and notable side effects, the description covers the main purpose, per-entry requirements, and the email behavior. It does not mention partial failure handling or return values, but given the absence of an output schema and the existing annotations, this is reasonably 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?

With 0% schema description coverage, the description compensates by explaining that each entry needs a role_id and either a username or an email. It clarifies the either/or relationship and hints at the side effect of email sending, which goes beyond the raw schema properties despite not detailing every field.

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 uses a specific verb ('invite') and clearly identifies the resource (project members) and the bulk scope. It distinguishes from sibling tools like membership_create by emphasizing 'multiple members' and 'in one call', making its purpose unmistakable.

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 clearly implies when to use the tool: when you need to invite multiple members in a single operation. It does not explicitly name alternatives or exclusions, but the bulk context is unambiguous and effectively differentiates it from the single-membership tools.

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