Update Frame Children

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

The description goes far beyond annotations by disclosing the internal prop (childElementIds), behavior for unresolved ids ('missing'), the automatic resizing logic, and the effect of passing an empty array. This gives the agent a clear model of side effects and edge cases.

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 compact yet information-dense, front-loading the core action before explaining edge cases. Every sentence adds value, and the structure flows logically from purpose to behavior to parameter nuances.

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 (multiple block types, ownership, resizing), the description covers all essential behaviors, including edge cases like missing ids and clearing ownership. With output schema present and annotations provided, the description is fully adequate for safe 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?

Though the schema covers all parameters, the description adds critical semantics: it explains the meaning of childElementIds as a full replacement list, clarifies padding's role, and specifies that resize is skipped when passing an empty array. This enriches the bare schema descriptions.

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 opens with a specific verb and resource: 'Replace a frame block's contents wholesale.' It clearly states what the tool does and distinguishes it from related tools like update_edgeless_block by focusing on frame ownership semantics.

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 provides strong usage context by explaining how the tool mimics editor behavior when dragging members into a frame, and when to use resizeToFit=false. However, it does not explicitly name sibling alternatives or state when-not-to-use this tool, so it falls short of a 5.

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