discord_admin_audit_log

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

The description aligns with the readOnlyHint annotation, confirming this is a read operation. It adds the detail that the tool uses Discord's standard filters, which gives context about how the tool behaves. However, it does not disclose further behavioral traits such as pagination, rate limits, or exact return format. With annotations covering safety, this is adequate but not rich.

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, front-loaded sentence that states the action and resource without any filler. It is entirely appropriate in size and structure.

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?

This is a moderately complex tool with 5 optional parameters and no output schema. The description is minimal but conveys the core purpose and hints at filter behavior. Given the annotations provided, it is sufficient for a straightforward read tool, but it lacks detail about return values and specific filter semantics that would make it more 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?

The input schema has 5 parameters with no descriptions (0% coverage). The phrase 'with Discord's standard filters' provides a conceptual link to the parameters (after, before, userId, actionType, limit) as being standard Discord audit log filters, which is useful. However, it does not explain each parameter individually, and with zero schema coverage, the description only partially compensates.

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 'Read' and the resource 'server audit log', making it easy to distinguish from sibling tools like discord_admin_messages or discord_admin_threads. It does not explicitly contrast with other admin tools, but the resource is specific enough to avoid confusion.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It only hints at 'Discord's standard filters', which implies usage context but does not directly state it.

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