Add Space 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 contributes one genuinely useful behavioral fact beyond that: the confirm=true gating requirement for user-requested actions. It does not say what state is destroyed or whether the change is reversible.

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, and the more informative confirmation requirement is placed second rather than front-loaded. The opening sentence is pure redundancy with the title, so the text is neither wasteful enough to score 2 nor efficient enough to score 4.

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?

This is a destructive mutation with six parameters, a nested payload object, no output schema, and no required fields. The description covers only the confirmation gate, omitting the payload/file exclusivity rule and the account credential-selection semantics — a significant shortfall for a tool of this complexity.

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 a middling 67%, and the description only speaks to one of six parameters (confirm). It says nothing about the mutually exclusive body-shaping options (payload vs. payload_file vs. body flags) or the email/space_id pair inside payload, all of which the description could have clarified.

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 first sentence, "Add Space Member," is a verbatim restatement of the title, which the rubric treats as tautology. The only added signal is the vague "Changes community state," which does not specify what resource is being modified or how this differs from siblings like create_space_group_member or remove_space_member.

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 states a confirmation gate ("requires confirm=true for the user-requested action") but gives no when-to-use vs alternatives guidance and no prerequisites. Sibling tools such as remove_space_member and get_space_member are not referenced, leaving the agent to infer selection from the name alone.

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