invite_workspace_member

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It does not mention whether an invitation email is sent, whether admin permission is needed, whether the action is reversible, or what happens if the member already exists — significant gaps for a mutating 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 two short sentences with no filler; the primary purpose comes first and the parameter note is minimal. Every sentence earns its place.

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 one-parameter invitation tool, the description provides enough to attempt a call, but it omits the expected outcome (pending invitation, email sent), potential errors, and permission requirements. Because there is no output schema and no annotations, these details would need to come from the description.

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 schema offers no property description (0% coverage), so the description's 'email (email of the new member)' does add the semantic context that the email belongs to the invited person. However, this mostly restates the parameter name and gives no format, uniqueness, or role expectations, so it only partially compensates for the schema gap.

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 identifies a specific action ('Invite'), a target resource ('new member'), and the scope ('current workspace'), which makes the tool's purpose clear. It does not explicitly distinguish itself from sibling tools such as create_organization_user or list_workspace_members, so it misses the top score.

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?

No guidance is provided about when to use this tool versus create_organization_user or other membership-related siblings, and there are no exclusions or prerequisites. The description only states what the tool does, not the conditions that should trigger it.

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