mysql_monitor_clients

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns a grouped processlist, which implies a read-only query, but it does not explicitly say it is non-destructive, does not require special permissions, or will not block. For a monitoring tool, this is a minor gap, but without annotations the transparency is only partial.

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 two concise sentences. The main purpose is front-loaded, and the usage scenario is stated in the second sentence. There is zero waste; every word contributes to the agent's understanding of what the tool does and when to use it.

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 parameters and an output schema is provided, the description covers everything essential: what it returns (grouped processlist) and a specific use case. It does not need to explain return values because the output schema covers that. For a simple monitoring tool, this is complete and sufficient.

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 tool has zero parameters, so the description has nothing to explain beyond the schema. According to the rubric, when there are 0 params, the baseline is 4. The description does not add parameter-related meaning, but none is needed. The schema already covers the empty parameter set.

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 exactly what the tool returns: a processlist grouped by user/host/command. This is a specific, differentiating statement that clearly distinguishes it from the sibling mysql_processlist, which presumably returns a raw processlist. The phrase also implies a specific resource (MySQL processlist) and a specific scope (grouping).

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 gives clear context for when to use the tool: 'Use to spot monitoring-agent connection storms.' This tells the agent a concrete scenario, though it does not explicitly name an alternative or state when *not* to use it. Since it doesn't exclude other tools or name a sibling, it falls slightly short of a 5, but the use case is clear and actionable.

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