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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description does add genuine context beyond that: the per-capita debt is benchmarked against similarly-sized communes, which tells the agent the output is comparative rather than raw. It still says nothing about response shape or limits.

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?

One dense, front-loaded line with no filler; every item listed adds scope information. It is a noun fragment rather than a structured statement, but nothing is wasted.

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 single-parameter read-only lookup with no output schema, the topic enumeration effectively acts as a return-value summary, which is enough for an agent to decide whether the tool is relevant. The only real gap is the absence of guidance on how it relates to the overlapping contract-award siblings.

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?

There is a single parameter with 100% schema description coverage; the schema already states 'Nom ou code INSEE' with an example. The description only reinforces the French-commune scope, adding no format details beyond the schema, so the baseline of 3 applies.

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 resource (the public finances of a French commune) and enumerates the four data domains it covers: debt, property tax rate, contract-winning companies, and public works sites. It does not, however, differentiate itself from siblings such as qui_remporte_les_marches, even though 'entreprises qui remportent ses marchés' clearly overlaps with them.

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?

Usage is only implied by the enumeration of covered topics, which suggests the kinds of questions the tool answers. There is no explicit statement of when to call it, no exclusions, and no routing to siblings that cover overlapping contract-award data.

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