query_history

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

Description declares 'Read-only' and lists returned fields (question, final SQL, status, row count, timestamp). This adds detail beyond annotations' readOnlyHint, offering practical behavioral insight.

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 concise sentences: main action, return fields, usage hint. Front-loaded and no redundant phrases.

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 output schema exists, description sufficiently covers purpose, return fields, and read-only nature. No missing context for a simple listing tool.

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?

Input schema covers both parameters with comprehensive descriptions (connection with examples, limit with default). Description adds no new parameter info, so baseline 3 applies.

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?

Description clearly states 'List recent query executions for a connection, newest first.' It specifies verb, resource, and ordering, distinguishing it from siblings like run_sql and list_connections.

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?

Explicitly says 'Use to review or reuse previously run queries.' This provides clear context, though it stops short of specifying when not to use it or direct alternatives.

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