db_processlist

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

With no annotations provided, the description discloses read-only nature, default summary behavior, and what the summary includes (saturation, session counts, oldest age, top 10 queries). Also notes prerequisite of db_profile and password from secret store.

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?

Description is concise with three sentences that front-load the purpose, explain default behavior, and list requirements. No unnecessary words, though a bit more structure could improve readability.

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 no output schema, the description adequately describes the summary output composition and mentions necessary prerequisites. Covers key aspects for a tool of moderate complexity.

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%, and the description adds context for 'full' (default vs raw) and 'app' (omitting for single-DB instances). This adds meaning beyond the parameter descriptions in 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 clearly states the tool shows DB connection saturation and a session summary, with specific detail on default summarized output versus raw dump via 'full=true'. It distinguishes from sibling 'db_top_queries' by focusing on overall process list rather than just top queries.

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?

Clearly explains when to use default summary vs passing 'full=true' for raw dump. Mentions the requirement for a db_profile and password from secret store. However, does not explicitly mention when not to use or compare to alternatives like 'db_top_queries'.

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