set_form_properties

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a mutation operation but does not describe which properties are affected, whether changes are reversible, what validation occurs, or what errors may arise. This is a significant gap for a write tool with no annotation safety signals.

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 one efficient sentence with no filler, and the main action is front-loaded. However, it is arguably too terse for a tool with six parameters and no annotation support, so it earns a strong conciseness score but not full marks for structure.

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?

The tool has six parameters, no annotations, and a minimal description that does not explain property semantics, selection prerequisites, or interaction with related form tools. Given the complexity and absence of structured guidance, the description is incomplete for correct invocation.

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%, and the description adds no parameter-level meaning. It does not mention name, text, items, checked, selected_index, or doc_id, so it fails to compensate for the schema's lack of descriptions even though the parameter names and titles are somewhat self-explanatory.

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 clearly states a specific verb and resource: setting properties on a form control, and specifies the scope ('currently selected'). It is distinguishable from generic property-setting tools like set_hwp_property, though it does not explicitly name a sibling or contrast with them.

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 insert_form_control, get_form_data, or set_field_ctrl_properties. The phrase 'currently selected' implies a prerequisite, but it does not explain how selection is established or what happens if no control is selected.

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