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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read. The description adds that the data is published per protocol, which is mild context, but says nothing about aggregation period, freshness, or scope. With annotations covering the safety profile, a 3 is appropriate.

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?

Two compact clauses with no filler. The main gap is that the front-loaded content is a noun phrase rather than an action statement, so the purpose is slightly obscured, but it is still efficient.

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 no-parameter read-only stats tool, the description covers what dimensions are returned and confirms protocol-compliant publication. However, it omits when to use it versus get_submission_status and gives no sense of aggregation scope or freshness, which leaves some ambiguity.

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 the baseline is 4. The description correctly describes the result set rather than trying to explain inputs, and no parameter documentation is needed.

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 enumerates what the tool reports (submissions received, accepted, refused, published; arrivals by discovery channel), which gives some substance. However, it never states a verb like 'retourne' or 'liste', so it reads as a list of data points rather than a clear action. It also does not distinguish itself from siblings like get_submission_status.

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 guidance on when to use this tool versus alternatives such as get_submission_status or get_guidelines. The clause 'Publié conformément au protocole' hints at a public-visibility context but does not tell an agent when to select this tool.

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