fill_form

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

Annotations already declare that this is not read-only, not open-world, and not destructive. The description adds a useful behavioral detail about checkbox values ('yes'/'no'), but it does not explain output behavior, overwrite behavior, or permission requirements.

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 description is two short, front-loaded sentences with no wasted words. It is concise, though its brevity contributes to the lack of parameter and usage detail elsewhere.

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 write tool with four parameters, nested values, and no schema descriptions, the definition is too thin. It does not explain the roles of 'path', 'output', or 'overwrite', nor does it provide sufficient context for correct invocation beyond the checkbox encoding convention.

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 carry parameter semantics. It partially explains the 'values' parameter by saying fields are filled by name and checkboxes use 'yes'/'no', but it leaves 'path', 'output', and 'overwrite' entirely undocumented.

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 gives a specific verb and resource: 'Fill form fields by name.' It clearly distinguishes this from generic PDF operations and implies form-field population, though it does not explicitly name or differentiate against the sibling tool 'list_form_fields'.

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?

There is no guidance on when to use this tool versus alternatives such as list_form_fields, nor any prerequisites or exclusions. The checkbox value convention is the only usage-oriented detail, but it does not address tool selection.

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