Get Audit Log

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

The annotations declare readOnlyHint and idempotentHint, and the description's verb 'Query' aligns with these. The description adds useful behavioral details about the limit default and maximum, which goes beyond the annotations. It does not describe the return format, but that is likely covered by the output schema.

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 a single, focused sentence that directly conveys the tool's purpose and key parameters. No unnecessary words or 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 output schema is present, the description does not need to detail return fields. It covers the essential query behavior and parameters. The brevity is sufficient for a simple read-only query tool, though it could mention filtering semantics (e.g., AND combination) for full clarity.

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?

The schema has no descriptions for its 6 parameters, and the description lists the filter names (event_type, symbol, account_id, date range, limit) without explaining their format or interaction. It adds the default/max limit info, but lacks details on date format or allowed event_type values, leaving some ambiguity.

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 verb 'Query' and the resource 'SQLite audit log', providing a specific scope. It does not explicitly name a sibling alternative, but the tool name and description are unambiguous enough to distinguish it from other query tools like get_quote or get_account_summary.

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 mentions filterable fields and the limit parameter, but does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or contextual cues. It is adequate for a straightforward query tool but lacks explicit usage guidance.

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