write_form_values

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the single-connection / open-once batching behavior and the shared capture-free addressing, which are real traits beyond the schema. However, it does not describe failure/partial-commit behavior, what 'save' toggles, or permission needs for a 12-parameter mutation 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-loaded with the core verb+resource and kept to a compact single sentence with tightly scoped parentheticals. Some internal-symbol jargon (NativeWriteSession) adds noise, but there is little wasted text.

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 12-parameter mutation tool with no annotations and no schema descriptions, the definition is too thin. An output schema exists (so return values needn't be explained), but the parameter semantics and save/failure behavior an agent needs to invoke it correctly are absent.

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 description coverage is 0% across 12 parameters, so the description must compensate but only touches 'values' (ordering) and 'field'/'base_field' addressing. Ten parameters such as save, capture, display, input_offset, and captured_value remain unexplained in both schema and description.

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 ('Batch value-write') and explicitly differentiates from the sibling write_form_value by noting it handles 'values in order' rather than a single value. Domain jargon (NativeWriteSession multi-write, capture-free field addressing) slightly muddies the plain-language purpose, but an agent can still tell it apart from the single-value writer.

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?

'Same as write_form_value ... but for values in order' implies the batching use case and hints at the alternative, but does not explicitly say 'prefer this over repeated write_form_value calls' nor state when-not to use it. Usage is inferred rather than spelled out.

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