List Audit Logs

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

Annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds that filtering is optional, which is already clear from the schema. No additional behavioral traits (e.g., pagination details, default sorting, or return format) are disclosed, but the minimal description is acceptable given 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 a single sentence of 15 words, efficiently stating the core action and optional parameters. It is front-loaded with the verb and resource, making it easy for an agent to quickly grasp the tool's purpose.

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?

The schema covers all parameter details, but the description lacks information about return values (no output schema), valid values for action and resourceType (no enums), and pagination behavior beyond parameter definitions. For a simple read-only list tool, this is adequate but not fully complete.

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?

All four parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description groups them as 'optional filtering', which adds a high-level context but does not enhance individual parameter understanding beyond what the schema already provides.

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 'Retrieve' and the resource 'audit logs', indicating a read operation. It specifies optional filtering, which aligns with the tool's purpose. However, it does not differentiate from the many other list tools among siblings, though the resource type (audit logs) is unique.

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 when audit logs are needed, but it provides no explicit guidance on when to use this tool versus alternatives or when not to use it. Since it is the only tool for audit logs, the context is implied but not stated.

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