describe_db_instance_databases

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

Annotations already convey readOnlyHint=true. Description adds that it is a batch operation, but does not disclose error handling, rate limits, or behavior for missing instances. Beyond annotations, value is limited.

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?

Description is very concise: one sentence for purpose, followed by parameter and return documentation. No unnecessary words, sentences are front-loaded with key action.

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 simple tool with output schema, description covers inputs and return type adequately. Missing batch size limits or error info, but not critical for a read-only batch retrieval 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 coverage is 0%, so description must compensate. It lists parameters and provides an example for db_instance_ids, adding some meaning beyond schema. However, it does not explain region_id format or constraints, and the example is basic.

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?

Description clearly states it retrieves database information for multiple RDS instances, using specific verb 'retrieves' and resource 'database information'. It distinguishes from sibling tools like describe_db_instances by specifying batch and database-level 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?

Usage is implied by the description (use when needing database info for multiple instances), but there is no explicit guidance on when not to use it or alternatives. No comparison to siblings is provided.

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