apply_actions

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

With no annotations, the description carries the full load and does so: it discloses the return contract (changes array plus one-to-one reasons, null when nothing changed, which key/rule caused rejection), the two persistence modes and version increment, and the side effect of embedding local image files. That is unusually complete for a mutation tool with zero annotation coverage.

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?

Core behavior and the two save modes are front-loaded, then the action catalog and guide pointers. The common-action enumeration is long but functional. Minor compression opportunity in the reasons explanation, which is slightly verbose.

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 complex mutation tool with a freeform actions array and no output schema, the description supplies the return shape, persistence semantics, and pointers to the authoritative action and document-model guides. Nothing essential to a correct first call is missing.

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%, so the baseline is 3, but the description adds real meaning the schema does not: documentId means in-place update versus document/documentPath meaning save-as-new, and that image src as a local path gets embedded. includeDocument is left to the schema, which is acceptable.

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+resource: apply a batch of edit actions to a document, evaluated by the same reducer used by the editor UI. The mutation/scoping story is explicit enough that an agent can distinguish it from get_document, validate_document, or render_document without opening any schema.

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?

Gives clear mode-selection guidance: documentId edits in place (version bumps), document/documentPath writes a new document and returns its documentId. It also routes the agent to get_guide("actions"), get_guide("document-model"), and the dingcard://schema/freeform resource for syntax. No explicit 'do not use this when…' exclusion against a named sibling, so it stops just 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.