sassy_audit_clear

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

With no annotations provided, the description fully carries the burden of safety disclosure. It explicitly states that the log is 'NEVER unlinked' and is 'always renamed to audit.cleared.<ts>.log,' which prevents a user from expecting destructive deletion. It also discloses the required confirmation value.

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 three short, purposeful sentences. The first sentence front-loads the action, the second provides key safety behavior, and the third gives the parameter requirement. Every line earns its place.

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 simple tool with one parameter and an output schema. The description covers purpose, safety, and the confirm gate. With an output schema present, return values need no explanation. Nothing important is missing for a tool of this complexity.

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 schema only shows a single optional string parameter with an empty default, offering no guidance. The description compensates by stating the exact required value: 'Pass confirm='YES' to proceed.' This adds meaning beyond the schema, though it does not explain what happens for other values or response details.

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 opens with a specific verb and resource: 'Rotate the audit log to a timestamped archive.' This clearly distinguishes it from sibling tools like sassy_audit_log (which likely retrieves logs) and sassy_audit_search (which searches logs) by emphasizing the rotation/archive behavior.

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 clearly implies when to use this tool: when you need to clear/rotate the audit log while preserving history. It also gives a concrete usage requirement: 'Pass confirm='YES' to proceed.' It does not explicitly exclude alternatives or name sibling tools, so it misses a 5.

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