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

No annotations are provided, so the description carries the full burden. 'Récents' hints at default ordering, but the description says nothing about pagination behavior for limit/offset, auth requirements, or that this is a safe read-only listing. That is a substantial gap for a list tool with no annotation coverage.

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 efficient sentence with the action and filters front-loaded and no wasted words. It is concise, though partly because it under-specifies rather than because it is optimally scoped.

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 output schema covers return values, but with 0% parameter coverage, no annotations, and 4 parameters, the description is too thin. It does not tell an agent enough about pagination, filtering semantics, or read-only safety to invoke the tool confidently.

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% with 4 parameters. The description adds meaning for only two of them (community_id and category) via the filter phrase, and gives no syntax or format detail. limit and offset remain 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?

The description states a specific verb (list/feed) and resource (actfiles) plus a scope qualifier (récents) and filter capability, which lets an agent distinguish it from get_actfile. However, 'actfile' is unexplained jargon and 'fil' is ambiguous (feed vs. thread), and no sibling is named.

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 explicit when-to-use guidance or alternative routing. The filter phrase 'filtrable par communauté ou catégorie' only implies a use case; it never says when to prefer this over get_actfile, mcp_list_actfile_comments, or a search tool.

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