dynamodb_describe_table

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It relies on the word 'Describe' to imply a read-only operation, but does not explicitly state it is a safe, non-mutating action, nor does it mention any prerequisites or error behaviors.

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, succinct sentence without unnecessary words. It is front-loaded and easy to parse, though it could include more information without being overly verbose.

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?

Despite having only one parameter, the description lacks context about what 'describe' returns (e.g., table status, throughput) and does not mention LocalStack-specific behavior. The absence of an output schema makes this minimal description insufficient for an agent to fully anticipate the tool's output.

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 schema covers the only parameter (tableName) with a clear description, and the tool description adds no extra semantic meaning. Since schema coverage is 100%, the baseline of 3 applies, and there is no additional value from the description.

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 ('Describe') and resource ('a DynamoDB table'), making it easy to understand the tool's core purpose. It distinguishes this from item-level operations like dynamodb_get_item, though it does not explicitly differentiate from dynamodb_list_tables.

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 such as dynamodb_list_tables or dynamodb_get_item. There is no mention of typical use cases like checking table status before other operations.

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