Clear Session Audit Log

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

Annotations already set destructiveHint:true. Description adds 'cannot be undone' which reinforces irreversibility. No additional behavioral context needed beyond the destructive nature and scope. No contradiction.

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 sentences with no waste. First sentence states action and scope. Second sentence warns of destructiveness. Front-loaded and efficient.

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 tool with no parameters and no output schema, the description fully covers what the tool does (clear audit log), scope (current connection), and critical behavior (destructive, irreversible). No gaps.

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?

No parameters (0 params, schema coverage 100% vacuously). Description adds no parameter info because none exist. Baseline 4 for zero-param tools.

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?

Description clearly states the action 'Clear the audit log' and specifies scope 'for the current connection'. Title reinforces the purpose. Distinct from siblings like get_session_log or list_audit_logs.

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?

Warns 'DESTRUCTIVE — cannot be undone' implying careful use, but does not explicitly state when to use or avoid, nor reference alternatives (e.g., use get_session_log to view first). Usage is implied but not fully guided.

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