Verify Output Dataset

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the check is scoped to the GP output root directory and that non-empty content can be demanded, which is useful but thin behavioral context beyond the annotations.

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 compact sentence with the verification target front-loaded and the optional constraint trailing. No filler.

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 both parameters are semantically covered for a low-complexity read-only verification tool. Only the relationship to similar existence/status tools is unaddressed.

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 carries the burden, and it does: output_path is identified as a dataset inside the GP output root directory, and require_nonempty is explained as requiring at least one record. Both parameters gain meaning the bare schema lacks.

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 ('核验' / verify) and resource ('GP 输出根目录内的数据集'), so the agent knows this checks post-run GP output rather than querying arbitrary data. It is distinguishable from dataset-existence siblings by its GP-output framing, though it never names those siblings.

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 the use case (confirm a GP tool actually produced its declared output) but gives no explicit when-to-use criteria and never routes the agent away from near-neighbors such as arcgis_pro_dataset_exists or arcgis_pro_analysis_result_status. Usage must be inferred.

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