project_features

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions projection but does not explain overwrite behavior, transformation method handling, error conditions, or that it creates a new feature class. Critical information for a mutation tool is missing.

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 a single sentence that directly states the tool's function with no fluff. However, it could be slightly longer to include crucial parameter and usage details without being verbose.

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 complexity of vector reprojection (requiring input, output path, CRS, optional transformation) and the lack of structured descriptions in the schema or output schema, the description fails to provide enough context for correct invocation. It omits details about overwrite behavior, transformation selection, and output characteristics.

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% and the description provides no additional meaning for any parameter. It does not explain the role of 'in_features', 'out_features', 'out_wkid', 'overwrite', or 'transform_method'. The agent receives no guidance beyond parameter names.

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 a vector dataset into another CRS/datum using the verb 'Transform' and specifies the resource as 'vector dataset'. This differentiates it from sibling tools like 'project_raster' (for rasters) and 'define_projection' (which assigns a 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 implies usage for reprojecting vector data, but provides no explicit guidance on when to use this tool versus alternatives like 'project_raster' or 'define_projection'. No exclusions or context are given.

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