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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered without the description. The description does add one genuinely useful behavioral fact beyond the annotations — that the setting applies forward to the next run rather than retroactively — but it says nothing about what is overwritten or whether the change is reversible despite destructiveHint=true.

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?

Nine words, but this is under-specification rather than conciseness. The fragment omits the verb entirely and is not front-loaded around an action, so a reader must fall back to the title and name to know what it does.

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?

For a destructive, non-idempotent mutation with three required parameters and no output schema, the description should say what changes, when it takes effect, and what is lost. It gives only the forward-looking scope and leaves the rest to the schema and annotations.

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 description coverage is 100%: project_id, the action const, and the sfx_level enum values are all documented in the schema. The description adds no syntax, format, or value semantics beyond that, so the baseline 3 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 is a noun phrase ('Storyboard settings, used by the next storyboard run') that never states a verb; the title carries the action. It does convey scope — settings that feed the next run — which distinguishes it somewhat from storyboard_generate/storyboard_read, but the purpose remains vague about what is actually being edited.

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 explicit when-to-use or when-not-to-use guidance. The clause 'used by the next storyboard run' weakly implies it should be called before generating, but the agent gets no instruction on alternatives (e.g., storyboard_generate) or on whether this must precede a run.

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