dynamodb_list_tables

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

There are no annotations, so the description must carry the behavioral disclosure. 'List all' conveys a read-only enumeration and 'in LocalStack' provides environment context, but the description does not mention pagination, response shape, rate limits, or explicit non-mutating behavior. It is minimally adequate for a simple list operation.

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, concise sentence that states the operation, resource, and scope without unnecessary detail. It is fully front-loaded and every word adds value.

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 list tool, the description is nearly complete: it specifies the resource (DynamoDB tables) and environment (LocalStack). However, since there is no output schema, an explicit note about the returned format (e.g., list of table names) would make it fully complete.

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?

This tool has zero parameters and the schema already covers this completely (100% coverage). With nothing to document, the baseline score of 4 applies, and the description does not need to add parameter details.

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 clearly states the verb 'List' and the resource 'DynamoDB tables', which immediately distinguishes this tool from sibling tools that target other AWS services. The addition of 'in LocalStack' sets the environment scope, making the purpose unambiguous.

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 clear context that this tool is for enumerating DynamoDB tables, and no sibling tool offers a similar alternative for this exact resource. It lacks explicit when-not or alternative usage guidance, so it does not reach a 5.

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