delete_community_space

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

Beyond the destructiveHint annotation, the description discloses permanent deletion with no undo, server-side auth injection, throttling to LearnWorlds' 30-per-10s cap, retry behavior on 429/5xx, and error-mapping details. This is rich behavioral context that annotations alone do not provide.

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 well-structured with compact labeled sections: Behavior, Returns, Use when. Every sentence adds operational value, especially the warning, persistence semantics, and alternative routing, with no fluff or repetition.

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 one-parameter destructive tool with no output schema, the description fully covers what happens on success, what non-2xx responses mean, auth handling, rate limits, and when to use it. Nothing an agent needs to invoke it correctly is missing.

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?

The input schema already documents the sole parameter 'id' as 'Unique identifier of the community space' with 100% coverage. The description only repeats this as 'provided space id' and adds no new format, source, or validation details, so the baseline 3 is appropriate.

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?

Opens with a destructive warning and HTTP verb, then states 'Deletes the community space specified by the provided space id.' This is a specific verb + resource statement and is clearly differentiated from the related update and unenroll operations mentioned later.

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?

Explicitly says 'Use when: only after the user confirms the removal' and directs the agent to the update/unenroll tools for non-destructive alternatives. This leaves no ambiguity about when this destructive tool should be invoked.

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