mysql_table_stats

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

With no annotations, the description must carry the burden. 'Get' implies a read-only operation, and the description lists what will be returned. However, it does not disclose any potential side effects, permission requirements, or edge cases (e.g., behavior when no table is specified). It adds useful return-value context but lacks deeper operational transparency.

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, focused sentence that is front-loaded with the action and resource. Every word contributes meaning, with no repetition or filler.

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 tool with two optional parameters and no output schema, the description sufficiently covers the return values (row count, data size, index size). The parameter behavior is fully documented in the schema. It is slightly thin on edge cases, but for the tool's simplicity, it is complete enough.

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 has 100% description coverage for both parameters (alias and table_name), so the schema already explains their meaning and optionality. The description adds no additional parameter-level context, keeping the score at the baseline for high schema coverage.

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 clearly states a specific verb ('Get') and resource ('table statistics') and details the exact statistics included ('row count, data size, and index size'). This distinguishes it from siblings like mysql_show_tables (list tables) and mysql_describe_table (structure).

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 usage is implied: use when you need table statistics like row count, data size, or index size. However, there is no explicit mention of when not to use it or which alternative tools to prefer (e.g., mysql_describe_table for structure), so it relies on 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.