Analyze Datasets

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that the operation touches three specific table categories and requires an enterprise write connection, but says nothing about cost, locking, or runtime impact on a large enterprise geodatabase.

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 short sentence with the scope front-loaded and no filler, but it is terse to the point of under-specification for a 6-parameter mutation tool; the brevity costs more than it saves here.

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 for a write-operation tool with 6 undocumented parameters and only annotations for safety, the description leaves too much unexplained. An agent cannot tell what include_system or the analyze_* flags actually do.

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 6 parameters, so the description carries the full burden and largely fails it: datasets, workspace_path, and include_system are never explained. The mention of 'base/delta/archive tables' loosely maps to analyze_base/analyze_delta/analyze_archive but does not clarify their semantics or defaults.

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+resource: updating statistics on enterprise geodatabase base, delta, and archive tables. This is far more specific than the tool name alone and distinguishes it from read/maintenance siblings like dataset_maintenance_info or rebuild_indexes, though it does not explicitly compare itself to them.

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?

It states a prerequisite ('requires enterprise write permission/write connection'), which is useful context, but gives no guidance on when to choose this tool over related maintenance siblings such as workspace_list_datasets, dataset_maintenance_info, or rebuild_indexes. No exclusions or alternatives are mentioned.

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