audit_audit_clear

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

No annotations are provided, so the description must fully disclose behavior. While 'Clear events' implies deletion, it does not warn that clearing is permanent or irreversible, nor does it mention permission requirements or side effects.

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, one sentence with a category prefix. It is front-loaded with the action and key parameter. However, it could include a bit more detail without becoming verbose.

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's simplicity and the presence of an output schema, the description covers the basic action, conditional parameter, and return format. However, it leaves ambiguity about when 'before' is null (clears all?) and the exact structure of the return object.

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 description adds meaning to the 'before' parameter by explaining its purpose ('timestamp to clear only older events'), but with 0% schema coverage, more detail (e.g., timestamp format) would improve clarity. The explanation is adequate but minimal.

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 action ('Clear events') and highlights the optional 'before' parameter to clear only older events. It effectively distinguishes this tool from siblings like audit_audit_export, audit_audit_get, and other clear tools such as cache_cache_clear or alert_alert_clear.

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 explains the use of the 'before' parameter but lacks explicit guidance on when to prefer this tool over alternatives or potential risks. It does not mention destructive nature or prerequisites.

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