get_footage_interpretation

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

With no annotations, the description must convey behavioral traits. It only states it is a read operation ('Get'), but fails to disclose any additional behavior such as required permissions, failure conditions, or side effects. The minimal description adds little beyond the tool name.

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 a single concise sentence of 7 words, containing no unnecessary information. It is well-structured and front-loaded, effectively conveying the tool's purpose without verbosity.

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?

Given the absence of an output schema and the complexity of the surrounding tools (many get/set siblings), the description is too sparse. It does not explain what footage interpretation settings are, what the return data structure looks like, or any error scenarios, leaving the agent with insufficient context for reliable usage.

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?

The single parameter 'item_id' has a full description in the input schema ('Node ID or name of the project item'), achieving 100% coverage. The tool description does not add any extra meaning beyond what the schema already provides, so the baseline score of 3 is 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 clearly states the action ('Get') and the resource ('footage interpretation settings for a project item'), distinguishing it from the sibling 'set_footage_interpretation' tool. The verb-resource pair is specific and 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 description implies usage when you need to retrieve footage interpretation settings, but it lacks explicit guidance on when to use this tool versus alternatives like 'set_footage_interpretation' or other get tools. No prerequisites or context are provided.

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