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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds a useful accuracy caveat ('Indicatif, topographie reelle = geometre') and confirms read-only behavior, but it does not add much beyond that about response behavior, permissions, 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?

The description is front-loaded with the call trigger, then compactly covers outputs, action modes, point format, caveat, and read-only status. It is dense but has no filler; every clause carries usage or constraint information.

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?

There is no output schema, but the description enumerates the kinds of results the tool returns: slope metrics, cut/fill volumes, balanced altitude, and advice. It could say more about action-specific prerequisites and return structure, but it is adequate for a read-only calculator with fully documented parameters.

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 100%, so the schema itself documents all four parameters. The description adds meaningful semantics for the action enum by mapping pente, volumes, and equilibre to concrete outputs, though it does not explain maille_m or altitude_plateforme beyond the schema.

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 verb and resource: analyzing terrain and earthworks from topographic points, then enumerates slope, cut/fill volumes, balanced platform altitude, and advice. This is clear and actionable, but it does not explicitly distinguish itself from nearby siblings such as cao_bim_geotechnique or cao_bim_vrd, so it stops 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 gives an explicit call trigger: 'Appelez quand vous devez analyser un terrain et son terrassement depuis des points topographiques,' and lists the action modes. It does not state when not to use it or name alternative tools, but the intended context is clear.

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