athena_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 burden. It communicates the operation type ('list') but says nothing about whether results are paginated, whether the operation is read-only, or what permissions are required. This leaves notable behavioral gaps for a tool definition with no safety annotations.

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 compact and front-loaded with the main action. The parameter lines are minimal but useful, and there is no filler or redundant phrasing. Every sentence earns its place.

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 simple two-parameter list operation with an output schema present, the description covers the essential invocation contract: what the tool does and what each parameter means. It does not address pagination or access details, but for this tool's complexity the description is reasonably 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?

The schema provides no property descriptions (0% coverage), so the description must compensate. It gives a meaningful one-line semantic for both required parameters, specifying that workspace_id is an Athena workspace id and database is a Glue database name. This adds disambiguation beyond the bare property titles, though it does not specify value formats.

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 states a specific verb and resource: 'List tables in a Glue database.' This clearly distinguishes the tool from siblings such as athena_list_databases and athena_describe_table. An agent can tell what this tool does without further context.

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 implies the natural use case—enumerate tables in a specified Glue database—but it gives no explicit when-to-use guidance or alternatives. Sibling tools like athena_describe_table or athena_list_databases are not referenced, so the agent must infer context from the tool name and wording.

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