fill_form_fields

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

No annotations are provided, so the description carries full behavioral burden. It discloses mutation behavior, duplicate-name refusal, missing-key semantics, the SDT skip behavior, auto-backup and rotation details, atomic validated save, and refusal of documents open in Word. This is extensive and highly useful.

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?

Every sentence adds substantive information about behavior, constraints, or alternatives. The main purpose is front-loaded, and the density is high without being bloated.

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 and the presence of an output schema, the description covers all essential operational facets: field types, accepted values, refusal modes, alternative routing, backup behavior, save guarantees, and an external blocker (open in Word). No critical context 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 description coverage is 0%, so the description must compensate for all parameters. It explains the 'values' mapping semantics, type constraints per field kind, 'missing' behavior, and the exact meaning of backup=False. Only 'file_path' is left implicit, but that is a standard path parameter.

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?

Description starts with a specific verb and resource: 'Set form-field values by name (legacy fields) or tag/alias (content controls)'. It distinguishes legacy fields from content controls and explicitly routes SDT types to set_content_control_value, making sibling differentiation clear.

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?

Provides concrete usage rules: text fields take strings, checkboxes take booleans, dropdowns only accept option values. It also names the alternative tool explicitly for SDT types, and explains the 'missing' parameter's two modes, so an agent knows when and how to use this tool.

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