Snapshot every camera in a scene

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the agent knows this writes output without destroying data. The description adds a genuinely useful behavioral detail, that each image is labelled with the camera's name, but leaves unsaid where the files are stored, whether previous snapshots get overwritten, and what happens if one camera in the scene fails.

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 well-formed sentence with zero filler, and the key information (batch across all cameras) is front-loaded before the labelling detail.

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 two parameters and no output schema, the description should tell the agent where results land and what shape the response takes, especially for a non-read-only tool. It covers the semantic labelling of results but not storage location, per-camera failure behavior, or the undocumented quality parameter.

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 carries the burden and does not meet it: the required `scene` parameter is never clarified (name vs. identifier) and the `quality` enum with its "high" default is not mentioned at all. Only the notion of a scene being targeted is echoed, which is already in the name.

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?

"Take a snapshot with every camera in the scene" states a specific verb and resource, and the scope word "every" implicitly separates it from the single-camera sibling camera_snapshot. It does not name that sibling outright, so an agent still has to infer the split, but the purpose itself is unambiguous.

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 phrase "every camera in the scene" implies batch usage, so an agent can reasonably infer when this beats a single-camera snapshot. However there is no explicit when-to-use statement, no mention of camera_snapshot or scene_compare as alternatives, and no prerequisites such as the scene needing to exist or be loaded.

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