run_show

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

Annotations already mark as read-only, and the description adds critical behavioral details: row limits (500 default, 1000 hard ceiling), INTO OUTFILE rejection, and timeout alignment with run_query. No contradictions.

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, each earning its place: purpose, constraints on statement, limits. Front-loaded and efficient with zero redundancy.

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 presence of an output schema, the description sufficiently covers all behavioral aspects for a read-only introspection tool. Includes limits, timeout, and statement restrictions.

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. Description adds value by explaining the sql parameter constraint (single statement, no INTO OUTFILE) and implicitly relates to row limits. Modest but helpful addition.

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 it executes SHOW introspection statements, distinguishing from siblings like run_query. It specifies constraints (single statement, no INTO OUTFILE), making the purpose specific and 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?

Provides clear context for when to use (SHOW statements) and constraints (row limits, timeout). Lacks explicit when-not-to-use alternatives, but the sibling tool names imply run_query for other queries.

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