get_sequence_bindings

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

Adds genuine behavioral detail beyond the annotations: the spawnable/possessable flag semantics and the caveat that possessable_count/spawnable_count are the movie scene's own counts and can disagree with those flags. The 'read-only' phrasing partly restates readOnlyHint, and idempotency/openWorld are left to annotations, so this falls just short of a 5.

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?

Front-loaded with the core action, then alternative routing, then return shape. It is dense but every clause carries information; the only mild redundancy is restating 'read-only' alongside the annotations.

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, the description supplies the full return shape (bindings, tracks, counts) and the subtle flag/count semantics. Combined with sibling routing and the name-resolution rule, an agent has everything needed to call and interpret it correctly.

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% so baseline is 3, but the description adds real meaning the schema lacks: sequence_name resolves to the first /Game asset matching case-insensitively. That naming and match-order semantics are not derivable from the schema's terse 'Name of the target Level Sequence.'

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?

States a specific verb and resource ('Lists every object binding of a Level Sequence') plus the resolution rule ('first asset under /Game whose name matches sequence_name (case-insensitive)'). It also explicitly distinguishes itself from sibling tools get_sequence_tracks and get_binding_tracks, so an agent can route without opening schemas.

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?

Names the alternatives and the exact conditions selecting them: 'Root tracks are not listed: use get_sequence_tracks' and 'For one binding's tracks with display names use get_binding_tracks.' It also states a prerequisite ('needs no open Sequencer'), leaving little to inference.

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