dynamodb_describe_table

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered by structured data. The description adds only the word "emulated" (useful signal that this targets a local emulator rather than real AWS). It says nothing about what metadata is returned (key schema, status, indexes) or the error behavior for a nonexistent table, which matters on a tool with no output schema.

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?

At four words it is certainly front-loaded and free of filler, but it is terse to the point of under-specification; there is no second clause supplying the missing usage or return-value context.

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?

Annotations cover the read-only/idempotent profile, which is the main behavioral risk. However, with no output schema and no parameter documentation, the description should say at least what the call yields and what the single argument identifies; for a describe operation, the returned metadata is the whole point.

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?

There is a single required parameter, "table", with 0% schema description coverage, so the schema alone does not tell the agent that it is the name of the table to describe. The description never references the parameter, so it fails to compensate for the coverage gap.

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 pairs a specific verb (Describe) with a specific resource (emulated DynamoDB table), so an agent can tell it retrieves table metadata rather than listing tables (dynamodb_list_tables) or reading items (dynamodb_get_item). It falls short of a 5 only because the distinction from siblings is implicit rather than stated.

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?

There is no guidance on when to use this versus dynamodb_list_tables or dynamodb_get_item, no prerequisite of the table already existing, and no note about what happens if the table name is unknown. The agent must infer all of this from the tool name alone.

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