dba_userSqlList

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

Annotations already declare readOnlyHint=true and idempotentHint=true, setting a baseline. The description adds value by explaining the persist parameter materializes a volatile table and returns its name, which is a key behavioral detail beyond the annotations.

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 clear purpose, usage guidelines, and argument list. The argument list is somewhat redundant with the schema, but it is helpful to have in-line. Minor room for improvement by relying more on schema.

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?

For a simple retrieval tool with good annotations, the description covers purpose, when to use, conditions, and parameters. It does not describe the output format (e.g., fields returned), but this is a minor gap given the tool name and context.

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?

With 100% schema description coverage, the baseline is 3. The description's argument list mostly repeats schema details, but it adds context by grouping parameters and emphasizing the required nature of user_name.

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 'Retrieve SQL statements executed by a specific named user', using a specific verb and resource. It explicitly distinguishes from the sibling tool dba_tableSqlList by specifying when to use each.

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 provides explicit when to use (user asks about a particular user's queries), when not to use (no user name mentioned), and an alternative (dba_tableSqlList for table-specific history). It also warns against empty user_name.

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