mysql_describe_table

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

With no annotations, the description must disclose behavioral traits. 'Get' implies read-only, but it does not mention error behavior on missing tables, permission requirements, or compatibility with views. It leaves room for ambiguity, though the read-only implication is clear.

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 sentence with no fluff. It is front-loaded with the verb and clearly conveys the tool's output, making it efficient to parse.

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 there is no output schema, the description provides a useful summary of the return contents (column structure, indexes, CREATE statement). However, it omits details about return format, error handling, or operational nuances, leaving moderate gaps for a simple describe tool.

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 already provides descriptions for both parameters (database and table), so schema coverage is 100%. The description only repeats 'for a table' and adds no extra parameter semantics, so it relies entirely on the schema.

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 'Get' and names three concrete outputs (column structure, indexes, CREATE statement) for a table. This clearly distinguishes it from siblings like mysql_query (arbitrary queries) and mysql_list_tables (just table names).

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 offers no guidance on when to use this tool versus alternatives. It does not mention use cases, when not to use it, or recommend alternatives such as mysql_query or mysql_list_tables, leaving the agent to infer context.

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