db_list_saved

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

With no annotations, the description must carry the behavioral disclosure burden. It does disclose that the list is scoped to the caller ('caller's saved'), which is useful, but it does not describe return behavior, pagination, ordering, or whether the operation requires authentication. 'List' implies read-only, but no explicit safety statement is provided.

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 extremely concise: one clear sentence for purpose plus a terse parameter note. No unnecessary filler; the key information is front-loaded.

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 tool's low complexity—one optional parameter, no required arguments, and an output schema present—the description is largely complete. An agent can correctly invoke it with no arguments or with a connection_id. Minor gaps around parameter provenance and behavior with null values are acceptable but prevent a perfect score.

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 description coverage is 0%, so the description must compensate. It does add meaning by explaining that connection_id is optional and used to filter the list, but it does not clarify what format the id should take, where it comes from, or the exact filtering semantics.

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 states a specific verb and resource: 'List the caller's saved DB Console queries.' This clearly identifies what the tool does and distinguishes it from sibling tools like db_list_connections (connections) and athena_list_saved (Athena saved queries).

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 the use case—listing saved DB Console queries—and mentions an optional filter, but it does not explicitly state when to choose this tool over alternatives such as athena_list_saved. There are no exclusion criteria or alternative routing guidance.

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