invite_member

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that invitations are sent 'via email', but does not explain side effects like whether acceptance is required, duplicate handling, permissions needed, or the nature of the resulting member 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 a single, direct sentence of about ten words with no filler. It front-loads the key verb and object, making it immediately scannable and appropriately sized.

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 simple 3-parameter invite tool with full schema coverage, the one-line description provides the basic purpose but lacks behavioral details such as what happens after the invitation is sent, the default role assignment, or expected output. The lack of annotations and output schema leaves room for more context, though the tool is relatively straightforward.

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?

The input schema is fully self-describing with descriptions for all three parameters, including the role enum and its default. The description adds little beyond 'new member' and 'via email', so it meets the baseline for high schema coverage without needing additional elaboration.

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'), the target ('new member'), and the channel ('via email'), which is specific and distinguishes this from sibling tools like remove_member or update_member_role. It conveys the core purpose unambiguously.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any exclusions such as existing members or domain restrictions. The phrase 'new member' implies scope but does not provide clear when-to-use or when-not-to-use context.

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