mysql_drop_access

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

Annotations declare destructiveHint=false, yet revoking access is inherently a destructive modification. The description does not disclose whether the revocation is reversible, what permissions are required, or what happens to existing connections. With no explanation, this is a significant gap.

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 concise and front-loaded, with two short sentences and parameter explanations in the Args section. No unnecessary information.

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 modifies access control, annotations are sparse and the description lacks critical details: required permissions, whether revoking access drops active connections, and success/failure behavior. An output schema exists but does not cover these operational aspects.

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 0%, so the description must compensate. It adds brief meaning: 'suffix' as the database name suffix and 'access' as the host to remove (including examples like IP, domain, localhost, or *). This clarifies the format of 'access' but the parameter semantics remain somewhat ambiguous without schema documentation.

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 states a specific verb+resource: revoke MySQL database access from a specified host. It clearly distinguishes itself from siblings like mysql_add_access or mysql_delete.

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 implies it removes an existing access entry, but does not explicitly state when to use it versus alternatives like mysql_delete or mysql_change_password. No prerequisites or exclusions are mentioned.

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