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

With no annotations provided, the description carries the full burden and does supply two useful facts: 'Lecture seule' (read-only, so no mutation risk) and the shape of the returned metadata (type, date, URL). It says nothing about pagination behaviour, the default/ceiling for limit, or what happens when the elu_id has no declarations or does not exist.

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 line with no filler: source, resource, scope and return fields in that order. It is terse to the point of under-specification rather than padded, which is the preferable failure mode but still leaves gaps.

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 two-parameter read tool with no output schema, the description does list the returned fields, which partly substitutes for a missing return contract. However, the undocumented limit parameter and the absence of any guidance on missing/empty results leave it only minimally complete.

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 coverage is 50%: elu_id is documented in the schema as a DataRespublica UUID, but the limit parameter (1–25) has no description anywhere. The description never mentions limit or any default, so it fails to compensate for the coverage gap on the second parameter.

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 names a specific resource (HATVP declarations, DataRespublica source) and its scope (linked to one elected official), which an agent can distinguish from the get_* siblings covering communes, departments, delinquency, DVF and scores. The list verb itself is carried only by the tool name, and 'HATVP' is unexplained jargon, keeping it short of a 5.

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?

It implies the tool is used for a given elected official, but gives no explicit when-to-use, no when-not-to-use, and no alternative tools for related data. An agent must infer from the name and required elu_id that this is a per-official lookup rather than a search.

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