Gp Export Table

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety characteristics are covered. The description adds that results are structured and that write/path restrictions depend on service capabilities, which is useful caveat context but not rich behavioral detail such as overwrite behavior or output format.

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 very short and front-loads the core purpose immediately. The second clause is somewhat generic boilerplate, but it still conveys a relevant constraint without excessive length.

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?

Although an output schema and annotations exist, the description omits parameter semantics and usage context for a write tool with two required parameters. An agent lacks enough information to know what in_table should reference or how out_path is constrained in practice.

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 both parameters are required, so the description must compensate for the schema's lack of documentation. It only vaguely references '路径限制' (path restrictions), which hints at out_path, and provides no meaningful semantics for in_table or out_path beyond their 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 names a specific verb and resource ('导出表' / export table), which is clear enough to identify the operation. It does not, however, distinguish this tool from sibling export tools such as arcgis_pro_gp_export_features or arcgis_pro_gp_table_to_table.

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 guidance is given on when to use this tool versus alternatives. The statement about write and path restrictions reflects service capabilities but does not tell an agent when this export is appropriate or what prerequisites are needed.

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