Describe

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds only vague claims ('verifiable structured results', 'write and path restrictions subject to service capabilities'), including a write-restriction note that is irrelevant for a read-only describe. It does not contradict the annotations, but adds little behavioral value.

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 and front-loaded, but the second clause is generic boilerplate ('write and path restrictions subject to service capabilities') that earns little space. Adequately sized but low information density.

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 needn't be explained. But for a describe tool with one undocumented required parameter, no usage guidance, and ~200 siblings, the description is far too thin to let an agent invoke it confidently.

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. The description says nothing about what form the path takes (dataset, layer, feature class, workspace), which is essential for a describe tool. It does not compensate for the coverage gap.

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 essentially restates the tool name/title ("ArcGIS Pro：描述describe") without stating what describing a dataset actually yields — geometry type, spatial reference, fields, extent, etc. "返回可验证的结构化结果" is generic boilerplate that could apply to any tool. No differentiation from sibling describe/info tools like arcgis_pro_dataset_schema, arcgis_pro_raster_info, or arcgis_pro_get_metadata.

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 indication of when to call this tool versus the many competing inspection siblings (get_metadata, layer_properties, table_properties, dataset_schema). The clause about write/path restrictions is a constraint statement, not usage guidance. An agent is left to infer context entirely.

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