List Transformations

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world. The description adds one useful behavioral detail beyond that: the first result is in ArcPy's recommended order. It does not disclose how the vertical or first_only flags alter the returned list, so it adds some but not rich context.

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?

A single efficient sentence with the listing action and key filters front-loaded, followed by the useful ordering caveat. No waste.

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?

Output schema handles return values and annotations cover safety, but with five parameters and zero schema descriptions, the missing vertical/first_only semantics leave the agent guessing. Enough to attempt a call, not enough to call confidently in all modes.

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%, so the description must carry parameter meaning. It mentions source/target WKID and an optional extent, but says nothing about the vertical flag or first_only flag, leaving two of five parameters undocumented anywhere.

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?

States a specific verb (列出/list) and resource (ArcPy 有效坐标转换/valid coordinate transformations), plus the key inputs (源/目标 WKID, 可选范围). No sibling tool competes for this purpose, so an agent can identify it immediately.

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 when the tool is useful (passing WKIDs to see transformations), but never states when to use it vs. alternatives or any prerequisites. There is no explicit when-not guidance, so routing is left entirely to inference.

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