add_invite_users_community_space

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

Annotations already declare write and non-destructive nature. The description adds valuable behavioral details: returning affected users (excluding duplicates) and the conditional invitation logic. It does not cover side effects like notifications or rate limits, but the added context is sufficient.

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 three sentences, front-loading the action and endpoint. Every sentence adds value: emoji + HTTP method, purpose, behavioral detail and return value. No fluff.

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 partially covers return value (array of affected users) and conditional behavior. It omits error cases, input limits, and authentication requirements, but for a moderate-complexity tool, it is fairly 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?

Schema coverage is 100%, so baseline is 3. The description reiterates the schema's parameter descriptions (uids as identifiers/emails) without adding new constraints, examples, or deeper semantics about usage.

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 tool adds/invites users to a community space, with a specific verb and resource. It distinguishes from siblings like 'remove_user_community_space' and other user-related tools by focusing on community space membership.

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 explains behavior based on the 'is_invitation_required' property, providing context for when invitations are sent vs direct addition. However, it lacks explicit when-not-to-use guidance and does not mention alternatives or prerequisites like permissions.

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