Список инстансов кластера

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

The description states a GET endpoint and 'returns a list', strongly indicating a read-only operation. However, annotations declare readOnlyHint: false and idempotentHint: false, which contradict the read-only, idempotent nature of GET. This is a clear annotation contradiction, reducing transparency to 1.

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, front-loads the purpose, and includes the endpoint without any wasted words. It is concise and well-structured.

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 one-parameter list tool with no output schema, the description adequately explains the resource and endpoint, but it does not describe the shape of the returned instances (e.g., fields, pagination) or address the annotation ambiguity. This leaves the agent with notable gaps in knowing what to expect from the response.

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 fully documents the single parameter db_cluster_id with a description and constraint. The description only echoes the parameter in the endpoint path and adds no additional semantic meaning, so with 100% schema coverage the baseline of 3 applies.

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 uses a specific verb ('Returns a list') and resource ('instances (databases inside the cluster)'), clearly distinguishing this from listing clusters or getting a single instance. The included endpoint further clarifies the exact scope.

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 when you need to list instances for a given cluster (requires db_cluster_id), but it does not explicitly state when to choose this over alternatives like list_database_clusters or get_database_instance. No exclusions or alternative tools are mentioned.

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