td_snapshot_scene

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false. The description confirms a capture operation but does not disclose key behaviors, such as whether a new snapshot is always created, if it overwrites existing snapshots with the same name, or what happens on repeated calls. Some behavioral context is missing beyond annotations.

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 a single concise sentence that front-loads the main action. It is information-dense without being verbose, though the parenthetical clarification could be slightly more structured.

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?

Given the tool's three parameters and presence of an output schema, the description provides the essential purpose but does not cover return value details (e.g., snapshot ID) or explain how the snapshot integrates with other snapshot tools. It is adequate but not fully comprehensive.

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%; each parameter (name, path, include_visual) is already described in the schema. The description's mention of 'structure + params; optionally visual' loosely correlates but does not add meaningful new semantics beyond the schema definitions.

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 clearly states the verb 'Capture' and resource 'scene snapshot,' and specifies the scope 'structure + params; optionally visual.' It effectively distinguishes the tool from sibling tools like td_list_snapshots, td_diff_snapshots, and td_restore_snapshot.

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 description lacks any guidance on when to use this tool versus alternatives, such as when to capture a snapshot vs. listing or restoring snapshots. No explicit context for usage is provided.

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