Enable Attachments

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely new behavioral context by stating the call requires a write toggle and a schema lock, which is an operational prerequisite not present in the annotations. It does not cover failure modes, but the added prerequisite is meaningful.

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?

Very short and front-loaded, putting the action first and the prerequisite second. No wasted clauses, though it is terse to the point of leaving gaps.

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 mutation identity is clear. Still, for a schema-modifying operation the description is thin: it omits what happens on failure (e.g., an active edit session or lock conflict) and gives no sense of the effect on existing attachment state.

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 dataset_path parameter, so the description carries the burden and largely fails to. It refers to 'a dataset' generically but adds no detail on path format, accepted dataset types, or how the path should be supplied.

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 (enable) and resource (attachments on a dataset), which cleanly distinguishes it from arcgis_pro_disable_attachments, arcgis_pro_add_attachments, and arcgis_pro_remove_attachments. It does not, however, explicitly name those siblings as alternatives.

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 gives a prerequisite (write switch and schema lock required), which tells the agent when the call is feasible, but it offers no explicit when-to-use/when-not framing relative to related tools like arcgis_pro_attachments_info or arcgis_pro_disable_attachments. Usage context is implied rather than stated.

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