dynamodb_put_item

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

With no annotations, the description must carry the full burden. It discloses 'create or replace', which is a key behavioral trait, but it omits other important details such as permissions required, whether the table must exist, return values, or that the entire item is replaced. The stated behavior is minimal and largely implied by the tool name.

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, front-loaded sentence that is concise and to the point. Every word earns its place, providing the essential information without unnecessary detail.

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 simplicity of the tool (two params, no output schema), the description is minimally adequate. It clarifies the create-or-replace behavior and the 'LocalStack' context, but it lacks usage guidance and details about item structure or error conditions. It is complete enough for a straightforward put operation but not comprehensive.

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 100% since both 'tableName' and 'item' have descriptions. The tool description adds no extra parameter meaning, but the baseline of 3 applies because the schema already handles 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 uses the specific verb 'Put' and explicitly states 'create or replace', clearly identifying the operation and resource (an item in a DynamoDB table). This distinguishes it from sibling tools like dynamodb_get_item, dynamodb_delete_item, and dynamodb_query.

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 (e.g., update_item or batch writes). The description does not mention when to choose put_item over other DynamoDB operations, leaving the usage context entirely to the agent's inference.

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