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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description adds genuine behavioral context beyond that — it is scoped to the user's own projects, flags the current project of this connection, and reports a page count per project — but says nothing about ordering, size limits, or what an empty result means.

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 compact sentence with the resource and payload front-loaded and no filler. Minor deduction because it is written in French while the rest of the tool surface (titles, sibling names) is English, which slightly slows matching against sibling tools.

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?

With no output schema, the description carries the burden of describing return values; it does partially (current-project marker, page count) but omits ordering, pagination, and whether projects from other workspaces or connections appear. Adequate for a zero-parameter read, but not full coverage.

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 tool takes zero parameters, so there is nothing for the schema to explain and nothing for the description to compensate for. Baseline 4 applies; no parameter-related claims are misleading.

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 identifies the resource ("Projets Outil de l'utilisateur") and even defines it ("un projet = un site + un domaine"), but uses a bare noun phrase with no verb, so the listing action comes only from the name/title. It also never distinguishes this from the many nearby project-related siblings such as list_site_projects, describe_site_projects, get_site_project, or switch_project.

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 when-to-use or when-not-to-use guidance and no mention of an alternative tool. An agent must infer from the name alone whether this or list_site_projects / describe_site_projects is the right call.

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