mysql_legacy_list_tables

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

With no annotations provided, the description carries the full burden. It explicitly discloses that the operation is read-only and names the exact SQL command, which is significant behavioral context for a tool. It doesn't discuss permission requirements or output details, but for a simple SHOW command this is reasonably transparent.

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 no filler. The primary action is front-loaded, the SQL semantics are compactly included, and the read-only trait is crisply stated. Every word 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 one-parameter listing tool with no output schema, the description is nearly complete: it says what is listed, how it is listed, and the database source. It could add a little more about output shape or permission behavior, but SHOW FULL TABLES is a well-known operation and the given context is sufficient in practice.

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 input schema provides only the 'database' string with min/max length and no description. The description's command template 'FROM <database>' clearly indicates that the parameter is the database whose tables should be listed, adding meaning beyond the bare schema. For a single obvious parameter this is sufficient compensation.

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 ('Lists'), a precise resource ('base tables and views'), and the implementation approach ('SHOW FULL TABLES FROM <database>'). This clearly distinguishes it from siblings like mysql_legacy_list_databases, mysql_legacy_describe_table, or mysql_legacy_ping.

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 intended usage is implied by the description: use this to enumerate tables/views in a given database. However, there is no explicit guidance about when to prefer this over sibling tools or any exclusions, leaving the agent to infer the decision.

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