get_footage_interpretation

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

With no annotations, the description carries the disclosure burden. It clearly signals a read operation and lists the relevant settings, but this is not much more than the tool name implies; it does not mention return shape, failure behavior, or side-effect-free guarantees.

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, front-loaded sentence with no filler; the parenthetical examples add useful specificity without bloating the definition.

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 simple one-parameter getter, the description is mostly sufficient, but with no output schema it does not indicate what the returned settings object looks like or whether values can be null. It also lacks an explicit pointer to the corresponding setter, so an agent must infer the full usage context from the sibling list.

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 coverage is 100% for the single projectItemId parameter, so the schema already documents it. The description adds only the phrase 'for a project item,' which is essentially redundant and adds no new semantic detail.

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 uses a clear verb ('Gets') and resource ('footage interpretation settings') and narrows scope to a project item, with concrete examples. It does not explicitly name the sibling setter, but the read verb and settings focus make the purpose 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?

Usage is only implied: use it when you need the current interpretation settings of a project item. No explicit guidance distinguishes it from set_footage_interpretation or other project-item tools, and no when-not-to-use conditions are given.

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