Disable Attachments

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds useful value beyond them by spelling out that the capability is disabled AND removed and that callers must supply confirm=true, though it does not say what happens to existing stored attachments.

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 front-loaded sentence with no waste, putting the destructive action ahead of the confirm requirement. It is arguably terse given the destructive nature of the operation, but nothing is padded.

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, and the destructive/confirm requirement is surfaced. Still, for a destructive schema-mutating tool it omits consequences (whether existing attachment records are lost) and the meaning of the required dataset_path.

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 must carry parameter meaning, and it only explains confirm=true for the confirm parameter. dataset_path's expected format (workspace path vs. layer name) is left entirely 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?

Names a specific verb (disable) and resource (dataset attachment capability), and adds that it also removes attachments. It is distinguishable from arcgis_pro_enable_attachments, but does not explicitly contrast with arcgis_pro_remove_attachments, which sounds closely related.

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?

States a precondition (a destructive switch and confirm=true are required), which implies when the tool applies. However, it never names alternatives or states when NOT to use it versus enable/remove/add attachments siblings, so the routing guidance is only implied.

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