form_open_settings

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

The description only says 'Open... via ИЗменить форму' without disclosing side effects, prerequisites, or failure modes. With no annotations, this minimal statement carries the full burden of behavioral disclosure and is insufficient for an agent to understand whether it changes UI state, requires a focused form, or can fail.

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 a single, short sentence with no filler, and the action and mechanism are front-loaded. It is as concise as possible, though the terseness comes at the cost of needed detail.

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 simple UI action the basic purpose is clear, but the undefined parameters, lack of usage context, and missing behavioral details make it incomplete for an agent. It does not explain what the customization dialog is, whether a form must already be open, or what session_id refers to.

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?

The input schema has two parameters, button and session_id, with defaults and zero description coverage. The description does not explain what either parameter means or how to populate them; the indirect reference to the button label is not enough to compensate for the complete lack of parameter documentation.

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 states a specific action: opens the current form customization dialog, and names the UI button label 'Изменить форму' as the mechanism. It distinguishes the tool from siblings like dynamic_list_open_settings by focusing on the current form, though it could be more explicit.

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?

No guidance is provided on when to use this tool versus siblings such as dynamic_list_open_settings, save_form, or close_form. The only implied usage is that a form must be current, but prerequisites, exclusions, and alternative routing are absent.

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