edit_model

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

With no annotations, the description carries the full burden and does so thoroughly: atomicity, merge/create semantics, null-field removal, delete/rename/move/scale behaviors, reference updates on rename, and automatic .R propagation are all disclosed.

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 definition is dense but compact: a one-line summary, then a terse op list where each line adds a distinct semantic. There is no filler and the most important framing (atomic batch) is front-loaded.

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?

The op vocabulary is exceptionally complete for a tool with no output schema and no annotations. The main gaps are the unaddressed top-level name/note parameters and lack of any statement about return values or error behavior, but the core invocation semantics are well covered.

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?

The description richly documents the nested ops structure, which is critical given the schema's 0% description coverage. However, it never explicitly ties the top-level 'name' parameter to the model being edited, nor explains 'note'; the op-level 'name' field could be confused with it.

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: 'Apply a batch of edits atomically.' It then enumerates the exact edit operations, making it clear this is the batch mutation tool for models and distinguishing it from read/list/export siblings.

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 clearly frames when to use the tool (batch edits that should be atomic) and adds the concrete constraint 'Edit only .L and centre elements; .R follows automatically.' However, it does not explicitly name alternative tools or say 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.