show_create_table

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

Annotations set readOnlyHint=true, and the description implies a read operation ('show create table'). The description adds no further behavioral details beyond what annotations provide, so it's adequate but not enhanced.

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 short but includes a labeled 'Args' section and 'Returns' line, which is somewhat structured. However, the opening line 'show create table db_name.table_name' is a command template rather than a natural description, and the overall length is acceptable but not optimized.

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?

With 4 required parameters and no schema descriptions, the description should provide more context about the tool's behavior and output. It only says 'Returns: the sql result,' which is vague. Although an output schema exists, the description remains incomplete for effective use.

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 schema has no parameter descriptions (0% coverage), so the description's 'Args' section adds basic meaning (e.g., 'dbinstance_id: The ID of the RDS instance'). This is helpful but minimal, providing only type and one-line description.

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 says 'show create table db_name.table_name' and 'Returns: the sql result,' which indicates the tool outputs the CREATE TABLE statement. However, it's phrased as a command rather than a clear purpose, and it doesn't distinguish from siblings like explain_sql or query_sql.

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 versus alternatives such as explain_sql or query_sql. The description lacks context about typical use cases or exclusions.

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