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 behavioral burden, but it only discloses the operation and parameter names. It does not say whether taking a snapshot mutates the scene, whether compare returns output, or what side effects occur, leaving significant behavioral ambiguity.

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?

The description is short and front-loaded with the core purpose, and the Args block is compact. It is efficient, though the snapshot_name line is redundant with the schema's property title and adds little information.

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?

Even though the tool is simple, there is no output schema and no annotation safety information, so the description should explain what taking or comparing snapshots does, how results are returned, and what happens to existing snapshots. That context is absent. An agent cannot confidently predict the tool's observable behavior.

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?

With 0% schema description coverage, the description does contribute meaning by listing the allowed values 'take' or 'compare' for action, which is useful since the schema has no enum. However, 'snapshot_name: Snapshot name' just restates the parameter title and adds no deeper semantics about scope, format, or behavior.

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 states a clear operation: 'Take or compare scene state snapshots,' and the action argument enumerates the two supported modes. It is understandable on its own, though it does not explicitly differentiate itself from similar sibling tools such as create_take or list_takes.

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?

There is no guidance about when to use this tool rather than snapshot- or take-related siblings, and no mention of alternatives or exclusions. The intended use cases are only implied by the phrase 'take or compare,' so an agent gets little routing help.

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