get_full_sequence_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'expanded operation,' which does not explain what data is returned, how large the response is, whether it is read-only, or what makes it different from other sequence inspection tools. 'Get' implies a read operation, but little else is disclosed.

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 and easy to scan, but the opening phrase 'Premiere Pro expanded operation' is generic filler that does not carry useful information. It is concise in length, but not in substance.

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?

With no output schema and no annotations, the description alone needed to explain what 'full sequence info' includes and how it relates to sibling tools. It does neither, so an agent cannot predict the return value or reliably choose between this and get_sequence_settings/get_sequence_structure.

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 has zero declared parameters, so there is nothing meaningful the description needs to add about parameter meaning. The schema's additionalProperties: true is unusual, but with no parameters to document, the baseline of 4 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 uses a specific verb and resource ('get full sequence info'), so the agent can tell it is a retrieval operation. However, 'full sequence info' is undefined and does not distinguish it from siblings like get_sequence_settings or get_sequence_structure, making it only a minimally clear purpose.

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 guidance on when to use this tool versus the many related sequence tools. No conditions, exclusions, or alternative tool names are provided, leaving the agent to guess which of the similar getters is appropriate.

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