describe_db_instance_parameters

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

Annotations already declare readOnlyHint=true, confirming a safe read operation. The description adds transparency by specifying the batch nature (multiple instances), the required fields (region_id, db_instance_ids), and the return type (list of dicts with ParamGroupInfo, ConfigParameters, RunningParameters). This enriches behavioral understanding beyond the annotation.

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 concise: one sentence for purpose, followed by parameter descriptions and return type. It is front-loaded and avoids unnecessary details. Minor improvement could be structuring the return as a sentence, but overall efficient.

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 presence of an output schema and sibling tools, the description adequately covers inputs and output structure. However, it lacks usage context or comparison to related tools, which would enhance completeness for an agent deciding between tools.

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?

With 0% schema description coverage, the description bears full responsibility for explaining parameters. It explicitly describes region_id as 'The region ID of the RDS instance', db_instance_ids as 'List of DB instance identifiers' with an example, and 'paramters' (correcting the schema typo) as 'List of parameter names' with an example. This provides critical semantic value absent from the schema.

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 starts with 'Batch retrieves parameter information for multiple RDS instances', which clearly states the verb (retrieves) and resource (parameter information for multiple RDS instances). This distinguishes it from sibling tools like describe_db_instance_attribute or describe_db_instance_performance, which focus on different aspects.

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 for batch retrieval of parameters but provides no explicit guidance on when to choose this tool over alternatives such as describe_db_instance_attribute or modify_parameter. No when-not-to-use or context hints are given.

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