get_audit_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 states the tool returns records of user and system activities and requires an Enterprise license, implying a read-only operation. However, it does not mention pagination, rate limits, or any side effects, which are minor omissions.

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 very concise with two sentences covering the essential information: the tool's purpose, the type of data returned, and the licensing requirement. No redundant or unnecessary content.

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 tool has an output schema, the description does not need to detail return values. It covers the purpose, examples of activities, and enterprise requirement. For a simple tool with two parameters, it is fairly complete, though pagination or result ordering could be mentioned.

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 description coverage is 100% with both parameters already described in the input schema. The tool description does not add any new information about the parameters beyond what the schema provides. A baseline of 3 is appropriate.

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 tool retrieves audit logs of activities in n8n (Enterprise feature). It specifies the resource ('audit log') and includes examples of activities. The tool is distinct from siblings that handle specific resources like workflows or credentials.

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 the tool should be used to get an overview of activities, not detailed info on a single resource. However, it does not explicitly provide when-not-to-use or name alternative tools. Adding a note about using get_workflow for detailed workflow info would improve clarity.

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