Изменение кластера базы данных

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows it is a mutating but non-destructive operation. The description adds the PATCH method and the set of modifiable parameters, which is useful, but it does not disclose side effects, auth needs, or behavior for omitted fields. No contradiction with annotations.

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 sentence that efficiently states the purpose and includes the API endpoint. There is no waste, and it is front-loaded with the key action and resource.

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?

With 5 parameters (1 required), no output schema, and no nested objects, the description plus schema and annotations provide sufficient context for a typical PATCH update operation. It lacks details about return values or potential side effects, but the openWorldHint annotation hints at broader impacts, and the description is adequate for an update tool.

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 100%, so all parameters already have descriptions. The description summarizes a subset of parameters (name, tariff, description, public network) but does not add new meaning beyond the schema. Baseline 3 is appropriate.

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 it changes database cluster parameters, listing specific fields (name, tariff, description, public network) and includes the API endpoint. This distinguishes it from other update_* tools like update_database_instance or update_database_admin.

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 implies usage by specifying the action and resource, but does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The context is clear but guidance is not explicit.

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