compare_snapshots

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

No annotations are provided, so the description carries the full burden. It does not say whether snapshots persist, whether 'take' overwrites an existing snapshot of the same name, where snapshots are stored, or what a comparison returns. For a dual-mode state tool with zero annotation coverage this is a significant gap.

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, with the core purpose in the first sentence. The raw 'Args:' block is minimally structured but not wasteful; nothing here pads the description.

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?

With no annotations, no output schema, and an underspecified dual-mode contract, the description is not complete enough. An agent cannot tell what compare yields or how take interacts with an existing snapshot name, which are the two things that determine correct 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%, so the description must compensate. It does add the meaningful part — that action accepts 'take' or 'compare' (the schema only declares a string with a default and no enum) — but 'snapshot_name: Snapshot name' is pure tautology and leaves naming/uniqueness semantics unexplained.

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?

The description names a specific verb pair and resource: take or compare scene state snapshots. That is clear enough to distinguish it from unrelated siblings like get_scene_info, but it does not differentiate it from the other comparison/snapshot-adjacent tools in a large sibling list, and 'scene state' is left undefined.

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?

No guidance on when to take versus compare, no prerequisites, and no mention of alternatives. The action values 'take'/'compare' are the only usage signal, and they are presented as a bare parameter listing rather than a when-to-use rule.

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