Compare every camera in a scene

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, which is unusual for a 'compare' operation and warrants explanation the description never gives. The only behavioral detail offered is that output is labelled with the camera's name. Nothing is said about what gets compared, whether snapshots are captured, where results are stored, or why the call is non-idempotent.

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?

It is short, but the brevity comes from under-specification rather than economy. The one sentence is not front-loaded with a clear verb, and its subject is a sibling tool's name, which is actively confusing rather than efficient.

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 three undocumented parameters, no output schema, and non-read-only annotations, the description leaves nearly everything an agent needs unanswered. It covers only the trivial fact that output is labelled per camera, which is not enough to call the tool correctly.

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% across three parameters, so the description must compensate and it does not: 'scene', 'quality' and 'baseline' are never mentioned. 'baseline' in particular is opaque — it is unclear whether it names a saved baseline, a camera, or a file — and the description gives no hint.

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 sentence gestures at the resource ('every camera in the scene') and mentions output labelling, so an agent can infer this compares all cameras in a scene. But it uses 'camera_compare' as if it were the verb, which is actually a sibling tool name, making the purpose read like a copy-paste artifact rather than a statement of what scene_compare does. It never says what a 'compare' produces or how it differs from the sibling camera_compare.

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 when-to-use guidance, no exclusion of alternatives, and no mention of the sibling tools camera_compare or camera_save_baseline, even though 'baseline' in the schema strongly implies coordination with camera_save_baseline. The agent is left to guess when a scene-wide comparison is preferable to a single-camera comparison.

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