dynamodb_list_tables

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral value is the word "emulated," which tells the agent results come from the local emulator rather than a live account. It says nothing about whether the call auto-creates state, how many tables are returned, or pagination 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?

A single four-word sentence with zero padding, and the resource is front-loaded right after the verb. It is efficient, though so terse that no secondary information (return shape, ordering) earns a place because none was included.

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 zero-parameter, read-only list tool with full annotation coverage and no output schema, the definition is adequate but thin: it does not say what is returned (table names only?) or whether ordering/pagination applies. The annotations and empty schema carry most of the weight, leaving only a small residual gap.

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 tool takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. No parameter text is needed and none is missing.

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?

"List emulated DynamoDB tables" names a specific verb (List) and a specific resource (DynamoDB tables), and the qualifier "emulated" scopes it to the local emulator rather than real AWS. It is distinguishable from siblings such as dynamodb_describe_table (single-table detail) and dynamodb_create_table, though it never states that contrast explicitly.

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 gives no when-to-use guidance, no mention of alternatives like dynamodb_describe_table for per-table detail, and no prerequisites. An agent must infer from the name alone that this is the discovery entry point before other DynamoDB operations.

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