List MySQL tables

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

With no annotations provided, the description carries the full behavioral disclosure burden. It states it lists tables and views but does not mention the default inclusion of views, how the 'selected database' is determined, output format, or any side effects. This is minimal coverage beyond the raw capability.

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, clear sentence that conveys the action, resource, and scope without any filler. It is appropriately sized for a list operation and front-loads the essential information.

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 list tool with no output schema and no annotations, the description gives a basic understanding of what it does. However, it lacks details about return format, behavior when database is omitted, and whether views are included by default. It is adequate but has clear gaps.

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 coverage is 100% because all three parameters (pattern, database, includeViews) have descriptions. The description's mention of 'current or selected database' adds slight context to the database parameter, but it essentially repeats the schema. Baseline 3 is appropriate.

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 'List' with the resource 'tables and views' and scopes it to 'the current or selected database.' This clearly distinguishes the tool from siblings like mysql_list_databases (lists databases) and mysql_describe_table (describes a single table).

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 provides context that the tool operates on 'the current or selected database,' implying use when you need to discover tables/views. However, it does not explicitly mention when to prefer this over siblings like mysql_describe_table or mysql_query, nor does it state any exclusions.

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