Clear session defaults

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

Annotation Contradiction: The description says 'Clear all session defaults' which is a mutating action, yet annotations declare readOnlyHint=true. This is a direct contradiction, and the description does not clarify the actual side effects or why the read-only hint is present.

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 concise sentence that is front-loaded with the action and resource, with no unnecessary words or repetition.

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?

The tool is simple, but the contradiction between the mutating description and readOnlyHint likely confuses an agent. It lacks context about persistence, idempotency, or the effect on session state, so it is incomplete for safe and correct invocation.

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?

Schema coverage is 100% and the schema already documents 'keys' as 'Keys to clear; omit to clear everything'. The description's phrase 'or only the listed keys' adds marginal value but does not elevate beyond baseline.

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 'Clear all session defaults, or only the listed keys' with a specific verb ('Clear') and resource ('session defaults'), and it distinguishes itself from sibling tools like session_set_defaults and session_show_defaults.

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 intended use is implied by the name and sibling context, but the description does not explicitly state when to prefer this tool over related ones (e.g., session_set_defaults) or mention any exclusions. It provides basic usage but no explicit when/when-not guidance.

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