describe_db_instance_accounts

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

Annotations already provide readOnlyHint=true, so the description adds only the batch nature and arg explanations. No additional behavioral traits (e.g., pagination, limits) are disclosed, but the read-only status is covered.

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 very concise—one line for purpose followed by structured Args and Returns. No extraneous text, front-loaded, each element earns its place.

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 tool (2 params, no nested objects) and existing annotations, the description covers purpose, args with examples, and return type. It omits potential limits on batch size but is largely complete for typical use.

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?

Despite 0% schema coverage, the description explains both parameters with specific examples: 'region_id' as region ID and 'db_instance_ids' with example values. This adds significant meaning beyond the schema's type-only definitions.

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 'Batch retrieves account information for multiple RDS instances,' specifying the verb (retrieve), resource (account information), and scope (multiple instances). This distinguishes it from siblings like describe_db_instance_databases or describe_db_instance_parameters.

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 use when needing account info for multiple instances but offers no explicit guidance on when to use this tool versus alternatives like describe_db_instance or other tools. No when-not-to-use or exclusion criteria.

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