Update Space Group

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, so the mutation/safety profile is covered. The description adds that it changes community state and mandates confirm=true, which is mildly useful context, but it does not say what is destroyed, what permissions are needed, or how partial updates behave.

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, front-loaded, with no filler or repetition. It is efficient, though the terseness borders on under-specification rather than being genuinely concise.

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 destructive 14-parameter tool with a nested payload object and no output schema, the description omits body-format selection, credential/account selection, and the scope of the state change. An agent would have to reverse-engineer most of the call contract from the schema.

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 only 43% across 14 parameters, so the description is expected to compensate, yet it mentions only confirm. The mutual exclusivity of payload vs body flags vs payload_file, the account credential selector, and the moderator id array are left entirely to sparse schema text.

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?

"Update Space Group" is a near-verbatim restatement of the tool name/title, so the first sentence carries no added information. "Changes community state" gestures at the resource but is vague and does not distinguish this tool from siblings like update_space, update_community, or update_paywall_group.

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 requirement, which is a precondition rather than a when-to-use statement. There is no indication of when an agent should call update_space_group versus update_space or update_community, and no exclusions or alternatives are named.

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