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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description adds real cross-tool context beyond them: earlier_renders means 'what a rollback can restore' and public_url is 'for view_image'. Those hints link returned data to segment_edit rollback and view_image usage, though return size/paging behavior is only implied.

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?

Two dense definition-style blocks keyed by the two action values, front-loaded with 'segments:' and 'segment_assets:' and no filler. It is efficient, but the absence of any lead sentence stating the tool's purpose makes the entry feel like a schema dump.

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 carries the response-shape burden and does so thoroughly for both actions (segment fields, asset fields, statuses, URLs, rollback data). It omits only an explicit purpose/usage statement, so an agent knows what comes back but must infer when to call it.

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 every parameter is already documented in the schema; baseline 3 applies. The description adds no parameter syntax or format detail beyond what the schema states (e.g. segment_number as a handle, limit=0 returns all) and instead spends its budget on return fields.

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 never states a purpose sentence; it documents the two returned shapes (segments, segment_assets). Combined with the title 'Read the storyboard' and the action enum, an agent can infer this reads storyboard data, but the description itself never says what the tool does and does not differentiate it from storyboard_edit or segment_edit.

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 or when-not-to-use guidance and no alternative named. The only routing information (segments vs segment_assets, paging via limit/offset) lives in the schema's action/limit descriptions, not the description text.

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