db_processlist

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

With no annotations, the description reveals read-only nature, default summary behavior, and the option for full dump. It discloses the requirement for db_profile and password. It could add more on error handling or missing prerequisites, but is adequate.

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?

Three sentences, no fluff. Key information is front-loaded: purpose, default behavior, option, requirements. Every sentence contributes meaning.

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 simplicity (two params, no output schema), the description covers purpose, behavior, prerequisites, and options. It provides sufficient context for an agent to decide and invoke. Could mention return format briefly, but not critical.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the effect of the 'full' parameter and that 'instance_id' is the identifier. It clarifies default behavior, which goes beyond schema descriptions.

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 shows DB connection saturation and session summary, with a distinction between default summary and full dump. It distinguishes from sibling tools like db_top_queries by focusing on current processlist.

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 explains when to use default vs full=true, and mentions prerequisites (db_profile, secret store password). However, it does not explicitly state when not to use this tool or suggest alternatives among siblings.

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