delete_system_logs

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

Annotations already mark this as destructive and non-read-only; the description adds that the tool forces rotation and creates a new log file. It does not disclose what happens to the existing log data beyond 'rotation' or mention any side effects or permissions, but it does not contradict the annotations.

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?

Two short sentences; the first is action-focused and front-loaded, and the second gives the endpoint. Every word earns its place with no filler.

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?

For a parameterless tool with annotations and an output schema, the description is sufficient to understand the core operation. It could be more explicit about the disposition of the old log file, but the action is simple and the destructive annotation fills part of that gap.

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 zero parameters and no required arguments, so there is nothing for the description to add. A baseline of 4 is appropriate for a parameterless tool.

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?

States a specific operation ('force log rotation' and 'create a new log file') on the system logs resource, so an agent can tell it apart from list_system_logs and other delete_* siblings. It is not a tautology, though it does not explicitly mention the 'delete' aspect suggested by the name and HTTP method.

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 action is described precisely enough that an agent can infer when to use it (when system logs should be rotated), but the description gives no explicit when-to-use/when-not-to-use guidance or alternatives. There are no caveats or exclusions, making the usage guidance implied rather than explicit.

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