mysql_processlist

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

With no annotations provided, the description carries the full disclosure burden. It does reveal one behavioral trait—'Truncates Info'—which is genuinely useful. But it omits other relevant behaviors such as the read-only nature of SHOW, potential privilege requirements, or whether it has performance implications. The disclosure is minimal but not absent.

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 three short sentences with zero wasted words. The core command is front-loaded, followed by a behavior note and a use case. Every sentence earns its place.

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 zero parameters and an existing output schema (which obviates explaining return values), the description covers the essential invocation context: what the tool does and when to use it. It could be slightly more explicit about the read-only nature, but the command name implies it, and the description is otherwise complete for a tool of this simplicity.

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 schema is trivially fully described and there is nothing to explain. Per the rubric, a 0-parameter tool earns a baseline of 4; the description adds no parameter details because none are needed.

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 names the exact SQL command 'SHOW FULL PROCESSLIST', making it clear the tool retrieves the MySQL process list. It also notes 'Truncates Info', adding a useful display detail. It doesn't explicitly distinguish itself from sibling mysql_active_queries, but the command name is self-explanatory and the intent is clear.

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?

'Use during a user-facing slowdown' provides a specific, actionable scenario for when to invoke this tool. However, it offers no guidance on when not to use it or mentions alternatives among the many sibling tools, so it stops short of an explicit exclusion.

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