load_group_system_snapshot

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds non-redundant context: loading 'does not mutate Live or recreate tracks', which clarifies it is a pure inspection/guard step and notes the 'compatible existing topology' precondition.

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 tightly written sentences, the core read action front-loaded and the non-mutation guarantee immediately following. No wasted words.

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 single-parameter read-only tool with full schema coverage and no output schema, the description covers purpose, non-mutation, and topology precondition. It could note what the returned capture contains, but nothing essential to correct invocation is missing.

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% for the single 'name' parameter ('Exact saved group-system snapshot name'), so the schema carries the burden. The description adds no syntax or naming detail beyond it, making the baseline 3 correct.

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 (Read) and resource (saved group-system JSON capture) with the scope 'one'. It implies a distinction from recall/save siblings via 'for review or guarded recall', but never names the sibling tools explicitly, so an agent must infer the boundary.

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?

'For review or guarded recall onto compatible existing topology' hints at the two usage modes, but gives no explicit when-to-use versus recall_group_system_snapshot, plan_group_system_recall, or save_group_system_snapshot. Usage 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.