clear_session

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

The description contradicts the annotations: it says 'Clear... ops', which implies a mutating/destructive action, while readOnlyHint is true. The description also fails to disclose side effects, scope, or post-conditions, which is especially problematic for a 'clear' operation.

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 a single short sentence with no filler. It is front-loaded and every word contributes to meaning, making it appropriately concise for such a simple tool.

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 zero-parameter tool the description is minimal, but it leaves unclear what 'ops' refers to, whether it clears only the current session, and what the observable result is. More importantly, the readOnlyHint contradiction makes the actual behavior uncertain. Missing output schema is a lesser concern here.

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 tool has zero parameters and the schema properties are empty, so there is nothing to document at the parameter level. The description adds meaningful context by specifying that all accumulated ops are cleared.

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 states a specific verb ('Clear') and resource ('all accumulated ops'), so an agent can understand that the tool resets accumulated operations. It is somewhat terse but not a tautology, and the tool name reinforces the session-scoped meaning.

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?

No guidance is provided about when to use this tool versus siblings such as get_session_status or delete_relation. There are no stated conditions, prerequisites, or exclusions, so the agent must infer usage from the tool name alone.

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