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

Annotations only declare write/non-idempotent/non-destructive; the description adds real behavioral context beyond them: it is project-scoped to the explicit project_id (no active-project guessing), it mutates the frame unless aspect=true, it returns the project identity, and it explicitly does NOT pick music, zoom, or sound. Those exclusions materially shape expectations for a batch WRITE.

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-loads the two most important tags (PROJECT-SCOPED, WRITE), which is good, but the middle is a run-on enumeration of A–J and nested clauses that is genuinely hard to parse in one read. It is information-dense rather than concise.

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 5 parameters, no output schema, and low coverage, the description should carry more burden. It conveys scoping and write behavior and hints at the return (project identity plus result), but without an output schema it never describes the returned frame/brief/proposals structure, and it leaves intensity and two pack enum values unexplained.

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 only 20% (project_id documented), so the description must compensate. It explains picks and aspect behavior and the pack letters, but omits the intensity enum values (calm/designed/charged) and the meaning of pack='auto' and pack='none', leaving half the parameters under-specified.

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 (apply) and resource (a genre/format pack) and enumerates the pack options A–J with their intent, and routes the agent to suggest_story for picks. The dense jargon ('edit about the edit', 'craft brief') makes it harder to gist than it needs to be, but an agent can distinguish it from siblings like suggest_story or set_frame.

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?

It implies a workflow: use picks=[numbers] from suggest_story, and E–J without picks return items for you to pick. But it never states when to choose this tool over apply_look, apply_recipe, suggest_story, or apply_edit_batch, leaving the selection decision largely inferred.

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