get_sequence_settings

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

With no annotations, the description carries the burden, and it does disclose the information returned (frame size, fps, pixel aspect, audio, render settings). However, it says nothing about read-only/error behavior or what happens when no sequence is active — gaps that matter when annotations are absent.

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 compact fragment with no wasted words, and the discriminating scope (active sequence) is stated up front. It loses a point only for being a verbless fragment rather than a clean sentence.

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?

No output schema and no annotations exist, so the description must convey return content — and it enumerates the setting categories in reasonable detail. It stops short of describing the structure or units of the returned values, but for a zero-argument getter it is largely sufficient.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies.

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 names the exact resource and scope — settings of the *active* sequence — and enumerates the settings returned (frame size, fps, pixel aspect, audio, render). It is a noun phrase rather than a verb-led sentence and does not explicitly distinguish itself from the nearby get_active_sequence, which keeps it at 4 rather than 5.

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 mention of prerequisites (e.g., an active sequence must exist), and no reference to alternatives such as get_active_sequence or get_sequences. Usage is only inferable from the content listed.

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