Create/Invite a community member

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only that it 'changes community state' and requires confirm, and the confirm rule is already stated in the schema's confirm field, so the marginal behavioral disclosure is thin.

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 short sentences with no filler, and the state-change/confirm constraint is front-loaded right after the purpose. Nothing redundant.

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 16-parameter, zero-required, nested-object mutation tool with no output schema, the description is far too thin. It omits the payload/body-flags/payload_file exclusivity rules and any indication of what a successful invite returns or requires.

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 description coverage is 38% across 16 parameters with nested payload/preferences objects, so the schema leaves substantial gaps. The description compensates by mentioning only confirm, saying nothing about the name/email payload, avatar signed_id, account credential selection, or the payload-vs-flags mutual exclusion.

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?

States a specific verb+resource ('Create/Invite a community member'), so an agent knows the operation. It does not differentiate itself from nearby siblings such as create_invitation, create_space_group_member, or update_member, leaving the boundary to be inferred from the name alone.

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 only guidance is the confirm=true gating for user-requested actions, which is implied usage rather than an explicit when/when-not. No alternative is named and no prerequisite (permissions, community context) is given.

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