mysql_table_stats

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

No annotations are provided, so the description carries the full burden. It does not disclose important behavioral traits such as whether the tool is read-only, requires specific privileges, locks tables, or how accurate the row count estimates are. The description merely states the output, not behavior.

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, no redundant words, and front-loaded. However, it is too minimal and omits crucial information, sacrificing completeness for brevity. It is adequately concise but not optimally informative.

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 tool's simplicity (2 parameters, no output schema), the description is incomplete. It does not specify the output format, whether it returns data per table or aggregated, or what 'size' refers to (data size, index size, etc.). The absence of output schema increases the need for description clarity, which is lacking.

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?

With 50% schema description coverage (only connectionId has a description), the tool description fails to explain the 'database' parameter. It does not add meaning beyond the schema, leaving the agent unsure about the database parameter's role or whether it is required.

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 ('Get') and lists the resources ('size, row count estimates, and index sizes'). It distinguishes from siblings like mysql_list_tables (just names) and mysql_describe_table (columns). However, it does not explicitly state that it returns stats for all tables in a database, which might cause ambiguity.

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 (e.g., mysql_query to calculate sizes manually, or mysql_list_tables for just names). There are no exclusions or prerequisites mentioned, leaving the agent to infer usage context.

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