revoke_mysql_privileges

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

No annotations are provided, so the description must disclose behavioral traits. It states 'revoke all privileges' indicating a destructive action, but does not clarify whether this removes the user entirely, whether it requires elevated MySQL privileges, whether the action is reversible, or what impact it has on existing sessions or grants. The description does not add context beyond the basic operation.

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 concise sentence with no unnecessary words. It is front-loaded with the action ('Revoke') and clearly states the scope. It earns its place with minimal overhead.

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 destructive mutation tool with no annotations or output schema, this description is under-specified. It lacks details on side effects, permission requirements, reversibility, and the extent of revocation (e.g., only on the specified database vs. global). While simple, the description is not complete enough for an agent to safely invoke it without additional context.

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 schema covers 100% of the parameters with clear descriptions ('Full MySQL username', 'Full database name'), so the baseline is 3. The description adds the context that 'all privileges' are revoked, which confirms that no privilege-specific parameter is needed—matching the schema's two parameters. However, it does not provide additional syntax or format details beyond the schema.

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 'revoke' and clearly identifies the resource: MySQL user privileges on a database. It distinguishes from the sibling 'set_mysql_privileges' which implies granting privileges, and 'revoke_postgresql_privileges' targets a different database type. This makes the tool's purpose unambiguous.

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. It does not mention that this is the counterpart to set_mysql_privileges, nor does it state any prerequisites (e.g., that the user exists, or that the database exists). The only implied usage comes from the tool's name, which is not explicit enough.

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