forget_session

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

The description adds real behavioral context beyond the annotations: no network contact occurs, `browser_profile` wipes cookies and device memory, and the service may re-challenge the device on next login. However, it never reconciles this deletion with the declared destructiveHint=false, nor states whether the removal is reversible or what happens to any other cached state for that service.

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 front-loaded sentences with no filler: the primary action first, then the optional flag's consequence. Every clause carries information an agent needs.

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 three-parameter mutation with no output schema and sparse annotations, the description covers the main behavior well but leaves the `profile` parameter undefined and does not clarify reversibility or the destructiveHint=false tension, so an agent still has gaps before calling it confidently.

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 only 33%, so the description must compensate. It does explain the effect of `browser_profile` (cookies, device memory, clean next login) in more depth than the schema, but the plain `profile` string parameter is never explained in either place, leaving an undocumented input.

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?

"Delete the local session for a service without contacting the service" gives a specific verb (delete) and resource (local session) plus a scope qualifier that implicitly separates it from the sibling `logout` (which presumably talks to the service). It stops short of naming `logout` as the alternative, so the distinction must be inferred.

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: forget the local session when you want a clean slate without a remote call. There is no explicit "use this instead of logout when..." routing, and no stated prerequisites or warnings about what happens to other local state.

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