Изменить данные аккаунта

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

Beyond the annotations, the description discloses two important behaviors: partial-update semantics ('остальные останутся как есть') and the onboarding gate where the API is fully closed until last name, first name, and birth date are present. This is rich, actionable behavioral context.

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?

Two sentences, front-loaded with the action, then parameter-use instruction, then the critical onboarding context. Every sentence carries operational value and there is no redundant restatement of the title or schema.

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 six-parameter, zero-required mutation tool with no output schema, the description covers the essential selection and invocation context: what it changes, how to perform partial updates, and when it must be used for onboarding. It does not describe the response format or exclusions, but the schema and annotations carry enough of that load.

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 already documents all six parameters, so the baseline is 3. The description adds meaningful semantics by instructing the agent to send only the fields to change and clarifying that unspecified fields retain their current values, going beyond the schema's individual field descriptions.

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 names a specific verb ('меняет') and a precise resource ('данные учётной записи'), then enumerates exactly which fields are affected: ФИО, дата рождения, телефон, часовой пояс. This clearly distinguishes account_update from generic account utilities and sibling tools.

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?

The description gives clear usage context: use it for partial profile updates and specifically for the acquaintance/onboarding step while the API is closed. It does not explicitly name alternatives or exclusions, but the context is strong enough for an agent to know when this tool applies.

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