get_parcelle_geometry

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

Discloses return format, data source, access restriction, and error condition (404). No annotations provided, so description covers key behavioral traits adequately.

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?

Extremely concise: 2-3 sentences covering purpose, output, usage context, and error. No fluff, front-loaded with main output.

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 simple one-parameter tool with no output schema, the description covers what is returned, data source, error condition, and access. Lacks mention of response size or rate limits but acceptable.

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?

The only parameter has a clear description in the schema; the tool description adds no further semantic detail beyond what's already there. Baseline 3 for high schema coverage.

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 clearly states that it returns precise geometry of the cadastre parcel as GeoJSON Polygon with surface area and Etalab ID. It distinguishes from siblings by contrasting with address-based lat/lng.

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?

Mentions the tool is for 'Plan Pro+ uniquement' and a specific 404 case, implying when to use and limitations. Could be more explicit about alternatives.

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