reset_setting

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

With no annotations, the description carries the full burden, and it does disclose the key behavior: a session-scoped override is removed rather than the underlying setting changed. However, it says nothing about idempotency, what happens if no override exists, whether other sessions are affected, or whether confirmation is returned for this mutation.

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?

A single tight sentence with the action front-loaded and the consequence trailing. No padding or redundancy; every clause earns its place.

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 low-complexity one-parameter tool with no annotations or output schema, the description conveys the semantic effect adequately, but it omits the parameter's meaning entirely and gives no failure-mode context for a mutating call. It is minimally sufficient rather than complete.

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 description coverage is 0% for the single 'key' parameter, so the description must compensate and it does not. It never states what form the key takes, which keys are valid, or how it maps to the override being removed, leaving the agent to guess.

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 verb and resource ('Remove a session override') plus the resulting effect ('so the profile value applies again'), which is more than a restatement of the name. It differentiates itself conceptually from get_setting/set_setting by naming the session-override layer, though it never names a sibling explicitly.

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?

Usage is implied by the phrase 'so the profile value applies again' — an agent can infer this is for reverting a temporary override. There is no explicit when-to-use guidance, no mention of the alternative set_setting for changing an override instead of removing it, and no prerequisites.

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