session_clear_defaults

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

With no annotations provided, the description carries the full burden. It clearly explains the effect: clearing pinned defaults and reverting to requiring them on every call, with a fallback note for serial. This is transparent about the behavioral change and the specific fallback behavior, which is valuable beyond what a schema could convey.

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 sentence, front-loaded with the action and resource, and includes a clarifying parenthetical about serial fallback. Every part is essential and there is no wasted text. It is perfectly sized for the tool's simplicity.

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?

Given the tool has no parameters, no output schema, and no annotations, the description fully explains what the tool does and its effect on session behavior. It is complete for this simple tool, though one could argue it could mention that it only affects the current session scope, but that is already implied.

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 schema description coverage is 100% (no params to describe). The description explains what the tool does without needing parameter details, which is appropriate. Since there are no parameters, the description adds value by clarifying the tool's effect, earning a higher score.

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 the tool reverts session-pinned defaults for project_dir and serial, causing them to be required on every call again. The verb 'clear' and the specific resources ('project_dir/serial defaults') give a precise purpose. It distinguishes itself from session_set_defaults and session_show_defaults among siblings.

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 implies this tool is used when you no longer want pinned defaults and want to require explicit parameters each time. However, it does not explicitly state when to use it versus when not to, nor does it name session_set_defaults or session_show_defaults as alternatives. The guidance is clear enough but lacks explicit context or exclusions.

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