camera.add_handheld

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

The description adds only 'Risk: standard; maturity: L3' which does not describe what the operation does or what side effects it has. Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the description contributes no meaningful behavioral disclosure.

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 but not meaningfully concise; it substitutes boilerplate about harness policy for a substantive statement of tool behavior. This is under-specification rather than efficient structure.

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 complex tool with 12 parameters and no rich schema descriptions, the description is grossly incomplete. It never explains what the command does to the camera or scene, what the output contains, or how the parameters relate to the resulting handheld motion.

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 12 parameters and only 25% schema description coverage, the description must compensate by explaining key parameters such as frameStart, frameEnd, seed, noiseScale, rotationStrength, and translationStrength. It does not mention any parameter, leaving agents unable to determine how to configure the handheld effect.

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 only restates the command name `camera.add_handheld` and provides generic harness metadata like risk and maturity. It does not state what adding a handheld camera does, the resource affected, or how it differs from sibling tools such as blender_camera_create or blender_camera_follow_path.

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 is given on when to use this tool versus alternatives. The mention of 'Per-request argument checks and session policy' is generic harness boilerplate and provides no actionable usage context or exclusion criteria.

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