aws_rds

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Manage' is extremely vague - it doesn't indicate whether operations are read-only or destructive, what permissions are required, whether changes are reversible, what happens on errors, or any rate limits. This leaves the agent with insufficient information about the tool's behavior.

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 maximally concise with a single four-word phrase. While this represents under-specification rather than ideal conciseness, from a pure length perspective, it's efficient with zero wasted words.

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 completely inadequate. It fails to provide the necessary context about how to use the tool effectively, what it returns, or how different actions work with different parameter combinations.

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 and 14 parameters (only 2 required), the description provides absolutely no information about parameters. It doesn't mention the 'action' parameter that drives the tool's behavior, doesn't explain what parameters are needed for different actions, and offers no guidance on parameter usage or dependencies.

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' clearly states the verb ('manage') and resource ('AWS RDS database instances'), making the purpose understandable. It doesn't specifically distinguish from sibling tools like aws_ec2 or aws_s3, but the resource focus is clear enough for basic differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like AWS credentials, doesn't explain when to choose RDS management over other AWS tools, and offers no context about appropriate use cases or limitations.

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