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

With no annotations, the description must carry the full behavioral burden. It does disclose one meaningful trait — that the operation is restricted to the community creator — but it omits irreversibility, what happens to members and content, and how auth_token is validated. Partial disclosure only.

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?

A single short sentence with the destructive action front-loaded and no redundant phrasing. It is efficiently structured, though its brevity leaves gaps that a destructive tool would ideally cover.

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, irreversible-style operation with no annotations, no output schema, and 0% parameter documentation, one sentence is insufficient. An agent lacks confirmation of permanence, cascading effects, and auth requirements needed to call this safely.

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 0%, so the description must compensate. It identifies the target entity (the community) but says nothing about community_id format or the required auth_token, leaving the second parameter entirely undocumented in both schema and description.

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?

States a specific verb and resource ("Supprime une communauté") plus a scope qualifier ("créateur uniquement"). It clearly differentiates the community resource from sibling delete tools (mcp_delete_actfile, mcp_delete_message, mcp_delete_user), though it does not explicitly contrast with mcp_leave_community.

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 parenthetical "créateur uniquement" implies who may invoke it, which is a usage precondition. However, there is no guidance on when to delete versus leave a community, and no statement of prerequisites or consequences that would direct an agent between alternatives.

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