feature_to_csv

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

With no annotations, the description carries the full burden. It discloses that the tool uses ArcPy ExportTable, writes to PathGuard allowed roots, and requires overwrite=true for existing files. These details provide adequate transparency for a read operation.

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 concise with three sentences: purpose, use cases, and behavioral details. No extraneous information. Front-loaded with the core action.

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?

The description covers input constraints, output behavior, and overwrite rules. With an output schema present, return values are not needed. It is complete enough for the tool's simplicity, though could mention error handling or large dataset considerations.

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 input schema already provides descriptions for all three parameters. The tool's description reinforces the PathGuard constraint and overwrite behavior but does not add significant new semantic information beyond summarizing the schema. Given high schema coverage, a score of 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 'feature class or table', and specifies the output format 'CSV'. It differentiates from sibling export tools by mentioning specific use cases (notebooks, data pipelines, reports, non-GIS tools).

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 explicitly states when to use the tool ('move attribute data into notebooks, data pipelines, reports, or non-GIS tools'), providing clear context. It does not explicitly mention when not to use or name alternative tools, but the context is adequate for an AI agent to decide.

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