query_log

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

No annotations are provided, so the description carries full burden. It only states 'show recent query audit log entries' without disclosing behavioral traits like ordering, time range, user scope, or whether it requires admin access. The description is minimal.

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 concise, using two sentences plus bullet-like parameter explanations. No redundant information, though the structure could be improved with clearer separation of purpose and parameter details.

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 an output schema assumed present, return values are covered. However, the description lacks context on ordering, time range, or user-specific scoping. Siblings help differentiate, but missing details limit completeness for an audit log 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?

Schema coverage is 0%, but the description adds value by explaining each parameter: 'connection: Filter by connection name (empty = all connections)' and 'limit: Maximum number of entries to return (default 20)'. This clarifies defaults and semantics beyond 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 'Show recent query audit log entries', specifying verb (show) and resource (audit log entries). It effectively distinguishes from siblings like 'describe_table' and 'query'.

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 implies usage for viewing audit logs but lacks explicit guidance on when to use this tool versus alternatives like 'query' or 'list_tables'. No when-not-to-use or prerequisites are mentioned.

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