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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so safety is covered. The description usefully enumerates the fields returned (institut, commanditaire, dates de terrain, échantillon, hypothèse, résultats bruts), which matters because there is no output schema, but it says nothing about how many polls are returned or what 'récents' means in time.

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 front-loaded sentence, with the scope ('récents de premier tour') first and the returned fields after. No filler.

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?

Since there is no output schema, listing the result fields is genuinely compensating, but for a no-parameter list tool the agent still cannot tell the recency window, the result ordering, or the likely result volume. Adequate but with real gaps.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema also forbids additional properties, consistent with taking no input.

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?

Names the resource precisely and scopes it: 'Sondages individuels récents de premier tour', plus the fields it surfaces. The 'premier tour' / 'individuels' framing implicitly separates it from get_runoff_polls and get_polling_average, but it never names those siblings explicitly.

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?

No statement of when to use this versus get_polling_average, get_trend or get_runoff_polls. 'Récents' is the only selection cue and it is undefined (no window, no count).

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