aws_rds

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. 'Manage' implies mutation capabilities, but it doesn't disclose critical traits like authentication requirements, potential costs of create/delete actions, rate limits, or that actions like 'delete' might be irreversible. It lacks context on what 'manage' entails operationally.

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, efficient sentence with no wasted words. It's appropriately sized for a high-level summary, though it lacks detail. The structure is front-loaded with the core purpose.

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 complex tool with 14 parameters, no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It doesn't explain the tool's scope, parameter meanings, behavioral expectations, or output format, leaving significant gaps for an AI agent to understand and use the tool correctly.

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 description provides no parameter information, while the schema has 14 parameters with 0% description coverage. Parameters like 'action', 'region', 'dbInstanceIdentifier', and 'masterPassword' are undocumented in both schema and description, leaving their purposes and formats unclear. The description fails to compensate for the schema's lack of documentation.

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 'Manage AWS RDS database instances' states the general purpose (managing RDS instances) but is vague about what 'manage' entails. It doesn't specify the specific actions available (list, create, delete, start, stop) or distinguish this tool from sibling AWS tools like aws_ec2 or aws_s3 beyond mentioning RDS.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., AWS credentials), compare to sibling tools (e.g., aws_cloudformation for infrastructure as code), or specify appropriate contexts for different actions like 'create' versus 'list'.

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