snapshot

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

No annotations are present, so the description carries full behavioral burden. It reveals the save/load action and that it affects arms and rifle parts, but omits whether saving overwrites an existing pose, what loading does to the current pose, required permissions, or any side effects.

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 concise sentence with zero waste. The parenthetical clarifying the pose's scope is front-loaded and useful.

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 tool with no annotations, no output schema, two required parameters, and 0% schema description coverage, the description is too thin. It lacks usage context, parameter detail, and behavioral transparency needed for confident invocation.

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%. The description faintly maps 'name' to a pose name and 'action' to save/load, but adds no format, constraints, uniqueness rules, or other semantics beyond what the bare schema properties imply.

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 ('saves or loads') and resource ('a named pose (the arms and the rifle's parts)'), so the agent knows it manages saved poses. It does not explicitly distinguish itself from siblings such as pose_idle, pose_clip, or load_rig, leaving some ambiguity about when snapshot is preferred.

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?

Provides no when-to-use guidance, prerequisites, or named alternatives. The agent must infer context entirely from the name and one-line description.

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