add_invite_users_community_space

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

Beyond the annotations, the description richly discloses behavior: it is a non-idempotent write that can duplicate effects, auth is injected server-side, calls are throttled and retried, and non-2xx responses surface as tool errors with specific status meanings. This fully compensates for and expands on the annotation hints. No contradiction with annotations.

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 long but well-structured with labeled sections for behavior, parameters, returns, errors, and usage. It is dense and information-rich, though the opening two sentences repeat essentially the same point, which is minor 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?

Given there is no output schema, the description thoroughly covers return values, error statuses, auth, throttling, idempotency, and when to use the tool. It provides everything an agent needs to invoke this tool correctly and interpret the result.

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 the baseline is 3, but the description adds important practical meaning: the entire payload goes in the single body argument, forwarded verbatim, and although the spec marks body optional, the endpoint expects one. This helps the agent avoid misusing the body parameter.

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 or invites users to a community space, with a specific verb, resource, and the conditional behavior based on is_invitation_required. It distinguishes itself from sibling tools like get_users_community_space and remove_user_community_space. The only minor issue is a slight redundancy between the first two sentences.

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 explicitly tells the agent when to use this tool ('only when the user asked to create this') and advises checking with a read tool first to verify the target exists and the record is not already present. It also names related community tools, giving clear routing guidance.

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