mysql_analyze_table

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 mentions that the tool is blocked in readOnly mode, which implies it may be considered a write operation, but does not clarify whether it is destructive or if it locks the table. The actual MySQL ANALYZE TABLE is read-only, creating potential confusion.

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 extremely concise with two sentences, front-loading the purpose. No unnecessary words.

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 has no output schema and low parameter coverage, the description lacks details on return values, errors, or behavioral side effects. It does not explain what the output of analyzing key distribution looks like, which is important for agent decision-making.

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 has a description). The description adds no parameter information; it does not explain what 'table' or 'database' mean or how they are used. With low coverage, the description should compensate but does not.

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 the action ('Analyze key distribution') and the resource ('MySQL table'). It distinguishes from siblings like mysql_describe_table (structure) and mysql_table_stats (statistics) by specifying 'key distribution'. The mention of readOnly mode adds context.

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 implicitly suggests use for analyzing key distribution but provides no explicit guidance on when to use this tool versus alternatives (e.g., mysql_table_stats). It does mention a condition ('Blocked when readOnly mode is enabled'), which is a useful constraint but not a full usage guideline.

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