list_audit_log

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

Discloses admin scoping, cursor pagination format (nextCursor = 'created_at|id'), max limit 200, and available filters. Without annotations, it covers essential behavioral traits well. Could add that it is read-only, but 'list' implies that.

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?

Four sentences, front-loaded with purpose and scoping. No redundant information; every sentence adds value.

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 no output schema, the description still explains pagination format and max limit. Parameters are fully covered in schema and description. For a list tool with 0 required params and 7 optional, it is 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?

Schema coverage is 100%, so baseline is 3. The description adds examples for eventType, explains cursor format, and clarifies scope. This provides meaningful additional context 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?

Clearly states it lists the audit log, scoped to account, and specifies the REST endpoint. No sibling tool duplicates this functionality, so it's well-distinguished.

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?

Explicitly mentions admin role requirement and that viewer/member get 403, giving clear context. Does not explicitly state when not to use or provide alternatives, but usage is well-understood.

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