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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Quitte une communauté' implies a membership mutation but does not state whether it requires specific permissions, whether it is reversible, what happens to the user's data or posts, or whether it affects the community for other users. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single short sentence, which is concise but also under-specified for a mutation tool with two required parameters. It is front-loaded but does not earn its place by conveying useful operational detail.

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?

The tool has no annotations, no output schema, and 0% schema description coverage for its two required parameters. The description fails to compensate for these gaps by omitting any behavioral, usage, or parameter context.

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%, and neither parameter (auth_token, community_id) is documented in the description. The description adds no meaning about parameter format, required values, or constraints, leaving the agent without guidance on what to supply.

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 states a specific verb ('Quitte' = leave) and resource ('une communauté'), so the action is unambiguous. It does not differentiate itself from the closest sibling mcp_delete_community or the reverse operation mcp_join_community, but the core purpose is clear.

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?

There is no guidance on when to use this tool versus alternatives such as mcp_delete_community or mcp_join_community. The description gives no prerequisites or context beyond the basic action, leaving the agent to infer usage.

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