Reset advisor session

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered; the description usefully adds what exactly is lost (stored state and call counter) rather than leaving it to the agent to guess. It omits whether the deletion is recoverable and what happens to the session afterwards, but the core destruction scope is disclosed.

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 tight sentences with the destructive action front-loaded and the usage condition second. Every clause earns its place and nothing is padded.

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 destructive, non-idempotent mutation with no output schema, the definition tells the agent what is removed and when to invoke it, but not the outcome for an invalid or already-reset session_id or whether the advisor session can be re-established. Adequate, with visible 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?

Schema description coverage is 0% for the single required parameter, so the description must carry the burden, and it only restates the parameter name ('for a session_id') without explaining where the value comes from, its expected format, or whether an unknown id errors or is a no-op.

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 ('Delete the stored state and call counter') and scopes it to a single session_id. The delete semantics inherently separate it from get_advisor_session, update_advisor_session and consult_advisor, though it never names those siblings 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?

'Use when the task is complete or the context has changed fundamentally' gives a concrete trigger condition that an agent can act on. It stops short of stating when not to use it (e.g. mid-conversation, or before harvesting results) or what to do instead of resetting.

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