Изменение инстанса кластера

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

Annotations already indicate non-read-only (readOnlyHint=false), non-destructive (destructiveHint=false), and non-idempotent (idempotentHint=false). The description adds the HTTP PATCH method and the fact it changes parameters, which is consistent. However, it does not disclose any side effects, required permissions, or behavior beyond what annotations already convey.

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?

A single, clear sentence that includes the HTTP method and path. It is front-loaded with the purpose and contains no filler, making it easy for an agent to parse.

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?

Given the simple update tool with full schema coverage and annotations, the description is adequate. It conveys the operation and endpoint, while schema handles parameter details. It could be slightly more explicit about which fields are updatable, but the schema already specifies optional name/description.

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%, with all four parameters described (required IDs and optional name/description). The description adds little beyond the endpoint path, which merely reiterates the required parameters. No additional semantic meaning is provided.

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 the tool 'changes database instance parameters in a cluster' and includes the endpoint PATCH /api/v1/databases/{db_cluster_id}/instances/{instance_id}. It clearly identifies the action and the specific resource (database instance in a cluster), distinguishing it from siblings like update_database_cluster and 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 provides the necessary context (updating instance parameters) but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. It is implied by the name and endpoint, but there is no direct guidance.

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