add_camera_focus_track

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that it is a thin wrapper and that the response is forwarded from add_property_track, including the 'saved' flag, but it does not describe side effects such as whether a section is always created or whether saving occurs automatically.

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 definition is front-loaded with the core action, followed by a single clarifying wrapper sentence and a compact return-value list. Every sentence earns its place, with no redundant restatement of the tool name or schema.

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 mutation tool with full annotation coverage and no output schema, the description is nearly complete: it explains the exact action, the wrapper relationship, and the forwarded response fields. It could go slightly further by stating prerequisites (e.g., a pre-existing camera binding) or save behavior explicitly.

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%, so the schema already documents sequence_name, binding_guid, and track_label. The description clarifies the target property (ManualFocusDistance) and binding context, but adds no syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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 precise verb and resource: 'Add a Float property track on ACineCameraActor::ManualFocusDistance to a Level Sequence binding.' It also explicitly labels itself as a 'Thin domain wrapper over add_property_track,' which distinguishes it from the general sibling tool.

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 implies usage through its concrete specialization (camera focus track on a sequence binding) and names add_property_track as the underlying general tool, but it never states when to prefer this wrapper over add_property_track or what prerequisites must hold. Usage is inferable but not explicit.

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