project_features

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

No annotations provided, so the description carries full burden. It discloses that the tool reads in_features, writes out_features within PathGuard allowed roots, requires overwrite=true for existing outputs, and supports an optional transform_method for datum differences. This adequately describes the write operation and key constraints.

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 (three sentences) and front-loaded with the main purpose. Every sentence adds relevant information without wasted words.

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 presence of an output schema and comprehensive schema descriptions, the description is fairly complete. It covers the main operation, constraints, and optional parameter. Minor missing details (e.g., error handling, licensing) are acceptable given the schema richness.

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 descriptions cover all parameters, so the bar is lower. The description adds value by explaining that transform_method is needed 'when datums differ' and that overwrite is for replacing existing outputs. This goes slightly beyond the schema baseline of 3.

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 tool transforms vector feature classes/layers into another coordinate system using ArcPy Project. It specifies the verb 'transform', the resource 'vector feature class or layer', and distinguishes from siblings like project_raster (raster) and define_projection (assigns CRS without transformation).

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 lists use cases: overlay, distance measurement, map export, analysis, alignment with other datasets. It implies by context (vector vs raster) when not to use, but lacks explicit alternatives or when-not-to-use statements.

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