Update Frame Children

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

Annotations show it's mutating but not destructive. The description adds rich behavioral context: missing ids returned under 'missing', ownership mapping matching editor behavior, resize logic, and skips when empty. This goes well beyond the annotations.

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 efficiently packed with essential details, front-loaded with the main action, and every sentence adds value. No redundancy or fluff.

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?

Given the tool's complexity, the description covers the core behaviors and edge cases. It lacks a full return structure specification, but does mention 'missing' ids. The parameter and behavior details are sufficient for correct invocation.

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%, but the description adds meaning to each parameter: childElementIds is a full replacement list, resizeToFit controls recomputation, padding is ignored when false, blockId is flavour-bound, and the empty array case. It also hints at return value (missing ids).

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 clearly states the verb 'Replace' and specific resource 'frame block's contents wholesale'. It distinguishes from siblings by specifying it handles both surface elements and edgeless blocks together, which is unique among the listed tools.

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?

The description explains the core usage (wholesale replacement), the effect of resizeToFit, and that passing `[]` clears ownership with skipped resize. It implies when to use this tool (for full replacement) versus potentially other tools (none for partial updates), but does not explicitly state when not to use it.

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