export_cadastral_dxf

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=true and destructiveHint=false. The description adds value by noting it is based on a continuous cadastral map and for reference purposes, and clarifies the default bufferMeters value and the ask-before-use convention, which supplements the annotations well.

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?

Two short, front-loaded sentences convey the main purpose and a key usage guideline with zero fluff. Every word serves a purpose.

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?

Given the parameter count and existence of annotations, the description is fairly complete. It explains the output format (DXF), the base map, and the buffer handling. However, it could mention what the DXF file contains (e.g., including neighbors) or clarify that crs and includeNeighbors are optional but well-documented in the schema.

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 description does not need to repeat parameters. It adds one extra piece of info: the default bufferMeters and the requirement to ask if omitted. This is helpful but not extensive. Baseline 3 is appropriate.

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 the verb 'export' and the resource 'parcel boundaries as DXF file by parcel address'. It distinguishes from siblings that use PNU codes (e.g., export_cadastral_dxf_by_pnu) by specifying address-based lookup.

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?

The description provides clear context for when to use (to export DXF by address) and includes a crucial guideline: if bufferMeters is not specified, ask the user first. However, it does not explicitly state when not to use or list alternative tools for PNU-based export.

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