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

Annotations only say it is a destructive write; the description goes well beyond by disclosing merge semantics (same form merged in array order and saved once), partial-failure semantics (per-field 'rejected' = unsaved, 'warnings' = saved), and sequential saving with guidance to check save status on communication failure. This is exactly the behavioral context an agent needs for a mutating batch tool.

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 purpose and batch limit, then adds merge, argument, and failure-handling detail, with no filler sentences. Dense but every line earns its place.

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?

An output schema exists so return values need not be described, and the description covers batch behavior, merge rules, and failure handling. The remaining gap is the unexplained per-item field structure, which it defers to fill_form.

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 0% and the single 'changes' parameter wraps a nested FormChange object with five undocumented properties (form_id, clear, sheet, values, from_profile). The description only says each item uses 'the same arguments as fill_form', a cross-reference rather than an explanation, so the field-level meaning is not supplied here.

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 ('複数様式を1回で記入する') and immediately scopes it (1〜50件), making it unambiguously the batch counterpart of the sibling fill_form. An agent can distinguish it from fill_form without opening either 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 context: it is for filling multiple forms at once (1-50) and each item uses the same arguments as fill_form, which implicitly routes single-form use to that sibling. No explicit when-not or exclusion statement is present, so it stops short of a full routing rule.

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