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

No annotations are provided, so the description must disclose behavior itself. It implies a read/list operation, but does not state whether authentication is required, whether pagination is supported, or how public/private visibility affects results. It adds little beyond the obvious.

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 front-loaded but severely under-specified for a tool with four parameters and no annotations. This is not concise; it is incomplete, lacking the detail needed to call the tool correctly.

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?

An output schema exists, so return values need not be explained. However, with no annotations and 0% schema description coverage, the description should explain parameter usage and basic behavior. It does not, leaving significant gaps for an agent to infer.

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 schema has four parameters (limit, query, offset, category) with 0% description coverage, and the description does not mention any of them. The word 'recherche' hints at a query parameter, but there are no details about filtering, pagination, or category usage, leaving the schema names to carry the full, undocumented burden.

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 clear resource (public communities) and two verbs (list/search), so the agent knows the general operation. It does not distinguish this tool from siblings like mcp_get_community or mcp_search_users, but the scope is still discernible.

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_get_community for a single community or mcp_search_users for user searches. The agent receives no exclusions, prerequisites, or context clues beyond the bare function.

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