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

With no annotations supplied, the description carries the full burden; it usefully discloses the data source (DataRespublica/INSEE) and that fiscal and security sections are conditional ('quand présents'), warning the agent some fields may be absent. It does not state what happens with an unknown or out-of-range commune code, whether values can be null, or any rate/coverage limits, which are notable gaps for a zero-annotation tool.

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 dense sentence that front-loads the tool identity, source, and territorial level before listing contents. It is jargon-heavy but every clause conveys content the agent needs given the absent output schema; no filler sentences.

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 compensates well by enumerating the returned fields (population, superficie, demographic series, DVF headline price, fiscal and security indicators). What remains missing is edge-case behavior on invalid commune codes and confirmation of read-only, non-mutating semantics, but for a one-parameter lookup this is close to sufficient.

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 one parameter with 100% schema description coverage, so the schema already explains commune_code including an example (69123) and length bounds. The description only reinforces the commune-level scoping via territoires.level=commune and adds no format, validation, or lookup semantics beyond the schema, so baseline 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 identifies a specific resource (commune-level INSEE fact sheet under territoires.level=commune) and enumerates its contents: population, area in km², INSEE demographic series, headline DVF price, fiscal and security indicators. Siblings like get_dvf_commune and get_delinquance_commune are implicitly differentiated by the word 'tête' (headline/summary) and 'quand présents', but the description never names a sibling or states the boundary 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?

Usage is only implied: an agent infers it should call this for a bundled commune overview and the specialized tools for deep dives on DVF or delinquency. There is no explicit when-to-use, when-not-to-use, or named alternative, so routing against get_dvf_commune, get_delinquance_commune, and get_departement is left to inference.

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