Get Metadata

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds a modest behavioral note that results are structured/verifiable and that path restrictions depend on service capability, which is genuine but thin additional 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?

Two short clauses, front-loaded with the action and with no filler, so it is not bloated. But the brevity comes at the cost of under-specification rather than efficient precision.

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 explained, and the annotations carry the safety profile. The remaining gaps are the undocumented dataset_path format and the absence of any sibling differentiation in a very crowded namespace, which leaves the definition only minimally complete.

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% for the single required parameter dataset_path, so the description carries the full burden of explaining it. It only alludes vaguely to "path restrictions" and never states the expected path format (workspace path vs. dataset name), which leaves the parameter essentially undocumented.

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 and resource ("读取元数据" / read metadata), which is clearer than a tautology. However it never says what kind of metadata (dataset, layer, raster, table) and does not distinguish itself from close siblings like arcgis_pro_describe, arcgis_pro_dataset_schema, arcgis_pro_raster_info, or arcgis_pro_table_properties.

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?

There is no when-to-use statement, no prerequisites, and no mention of alternatives or when-not-to-use. The trailing clause about write/path restrictions being subject to service capabilities is a caveat, not routing guidance, so the agent gets no help choosing between this and the many similar read tools.

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