list_tables

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

With no annotations, the description carries the full burden of disclosure. It implies a safe, read-only listing with no arguments, but does not state whether results are permission-scoped, whether pagination applies, or how many tables to expect; low inherent risk keeps this from being a serious gap.

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?

Two short sentences with zero filler, and the sequencing instruction is placed where it will be read immediately. Nothing is repeated from the title or schema.

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?

An output schema exists, so the description needn't explain the return shape, and a zero-parameter tool has little else to document. What remains missing is only minor context such as whether this is the entry point for all shop-database work or whether other databases exist.

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 tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no inputs are required, but adds no further detail such as whether a database argument might someday be needed.

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?

States a specific verb and resource (list tables) plus the scope (the shop database), which is more than a restatement of the name. It does not explicitly distinguish itself from siblings like describe_table or run_query, so an agent must infer that this returns names rather than structure or query results.

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?

"Call this first" gives an explicit sequencing instruction that tells the agent to invoke this before describe_table or run_query. There are no stated exclusions or alternate paths, and no mention of what to do if the listing fails or is empty, but the when-to-use context is clear.

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