Gp Project

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

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered elsewhere. The description only adds a vague hedge that "write and path restrictions depend on service capabilities" without saying what gets created, overwritten, or what permissions are needed.

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?

It is short, but brevity here is under-specification rather than efficiency: two clauses, neither of which conveys actionable information for a 4-parameter geoprocessing operation.

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?

An output schema exists, so return values need not be described, but with 0% schema coverage and no parameter guidance the definition is not complete enough for an agent to call this tool correctly. The generic write/path caveat does not compensate.

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% across 4 parameters (in_dataset, out_dataset, out_wkid, transform_method), and the description adds zero meaning — it never explains what in_dataset/out_dataset accept, what out_wkid is, or that transform_method is optional. The full burden fell on the description and it was not met.

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?

"ArcGIS Pro：project工程" essentially restates the tool name and title; it never says this reprojects a dataset from one coordinate system to another (the role implied by out_wkid/transform_method). The trailing clause about "返回可验证的结构化结果" is generic boilerplate, not a purpose statement.

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?

No indication of when to use this tool, no prerequisites, and no routing to the obvious alternatives such as arcgis_pro_gp_project_raster for rasters or arcgis_pro_set_map_spatial_reference for view-level CRS changes.

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