dba_tableSqlList

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

Annotations already indicate read-only and idempotent. The description adds behavioral context about the 'persist' parameter materializing a volatile table and returning its name, which is useful beyond the annotations. However, it does not discuss authentication, rate limits, or other constraints.

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 well-structured with a purpose paragraph and a parameter list. It is concise but covers essential points; could be slightly tighter but is effective.

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?

With no output schema, the description does not explain the return format (e.g., whether it includes timestamps, SQL text). While the purpose and usage are clear, a bit more detail on what the result contains would improve completeness. The parameters are fully described.

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 description coverage is 100%, so baseline is 3. The description repeats parameter names and gives brief explanations, which are nearly identical to the schema descriptions, adding minimal extra value.

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 action ('Retrieve SQL statements') and resource ('against a specific named table'). It distinguishes from the sibling tool 'dba_userSqlList' by specifying that this tool is for table-specific history, not user-specific history.

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?

Explicit guidance is given on when to use (user asks about queries on a particular table), when not to use (if table name not explicit, ask for clarification), and alternative tool (dba_userSqlList for user-specific SQL history).

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