MySQL JSON Array Append

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false), so the description must carry the burden. It only states 'Append a value', which implies mutation but provides no details on side effects, error behavior (e.g., if path doesn't exist), or whether previous data is preserved. Missing critical behavioral context.

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, which is concise but too sparse for a tool with 16 parameters and complex behavior. It lacks structure or front-loading of critical information (e.g., required parameters, output).

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 high parameter count and vague parameter descriptions, the tool's complexity demands a richer explanation. There is no mention of return values (though an output schema exists), prerequisites, or typical usage patterns. The description is far from complete.

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 lists 16 parameters with many aliases (e.g., col, sql, val, filter, condition). The descriptions are mostly 'Alias for ...', adding little clarity. For example, 'sql' is described as 'Alias for where', but it's unclear which parameters are primary. The description does not explain how to use the path, value, or column parameters beyond the schema's brief text.

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 tool appends a value to a JSON array at a specified path, which is a specific verb and resource. It does not distinguish from sibling tools like mysql_json_insert or mysql_json_set, but the purpose is unmistakable.

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 provides no guidance on when to use this tool versus alternatives such as mysql_json_insert or mysql_json_set. There is no mention of prerequisites, typical use cases, or conditions that make append preferable.

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