export_to_shapefile

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

With no annotations, description must carry full behavioral burden. It discloses that the tool reads input and writes shapefile components into an existing output folder within PathGuard allowed roots. However, it does not mention overwrite behavior, error handling, or performance implications.

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?

Three sentences: core function, usage guidance, and behavioral context. No redundant information. Well-structured and front-loaded.

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 tool's simplicity and presence of output schema (not shown but indicated in context), the description covers purpose, usage, and basic behavior. Could mention output file naming or limitations for completeness.

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 description coverage is 0%, but the schema itself provides parameter descriptions. The main description does not add meaning beyond the schema; it merely references 'in_features' and 'output_folder' without additional context.

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', resource 'feature class', and target format 'shapefile', using the ArcPy function. It distinguishes from siblings like 'export_to_geojson' and 'export_map_as_image'.

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?

Explicitly says 'Use this when data must be shared with legacy GIS tools or systems that require shapefiles', providing clear context. Does not explicitly state when not to use, but sibling tools imply alternatives.

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