save_device_chain_snapshot

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

Annotations only cover the generic safety profile (mutating, non-idempotent, non-destructive), while the description adds real behavioral scoping: 'Never overwrites' and the explicit exclusion list ('Does not save hidden plugin state, samples, automation, or mappings') tells the agent what will and will not be captured. It stops short of describing failure modes or what happens when the name already exists.

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?

Two sentences, front-loaded with what is captured, followed by the never-overwrites guarantee and the exclusion list. The first sentence is dense but every clause conveys scope-relevant information. Little waste, though the sentence could be slightly tightened.

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?

For a save tool with no output schema, the description covers what is captured, where it goes, and what is deliberately omitted, and the annotations cover the safety profile. The main remaining gap is error/overwrite behavior when a name already exists ('Never overwrites' implies it, but the resulting behavior is unstated).

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 100% and the schema itself documents the name charset restriction and the trackId ID format, so the description is not required to carry parameter detail. The description adds only the indirect hint that 'name' populates a named library entry; baseline 3 applies.

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 (Capture/save) and resource (device chain snapshot) plus the destination (private named local chain library), which is meaningful detail. It does not explicitly distinguish itself from the near-identical sibling capture_device_chain_snapshot, so the boundary between in-memory capture and persistent named save is left to inference.

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 phrase 'private named local chain library' implies this is the persistent, reusable-snapshot path, but the description never names an alternative or states when to prefer it over capture_device_chain_snapshot or capture_device_parameter_snapshot. Usage is inferred rather than stated.

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