mysql_describe_table

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

The description correctly indicates a read operation ('Show column definitions and metadata'), which is the primary behavior. However, without annotations, it does not disclose additional behavioral traits such as error handling (e.g., table not found) or permission requirements, which are typical for database metadata tools.

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 with no superfluous words. It is concise and front-loaded, immediately conveying the tool's purpose.

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?

Given the three parameters and no output schema, the description is incomplete. It does not specify what 'metadata' includes (e.g., type, nullability, keys), nor does it mention that this corresponds to SQL commands like 'DESCRIBE' or 'SHOW COLUMNS'. The optional database parameter's default behavior is unclear.

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 description coverage is only 33% (only connectionId is described). The description adds no parameter-level details beyond what the schema provides. The 'table' and 'database' parameters lack descriptions both in the schema and in the tool description, leaving ambiguity about their format or default behavior.

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 a specific verb 'Show' and clearly identifies the resource as 'column definitions and metadata for a MySQL table.' This distinguishes it from sibling tools like mysql_list_tables or mysql_show_create_table, which have different purposes.

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?

No guidance is provided on when to use this tool instead of alternatives such as mysql_show_create_table or mysql_list_views. There are no hints about prerequisites or context where this tool is appropriate.

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