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

No annotations are provided, so the description carries the full burden. It vaguely implies a destructive discard ('leave behind') and a conditional side effect ('enters the haven'), but never states whether the discarded content is recoverable, what permissions are required, or what the return looks like.

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 short sentences, front-loaded with the action. The redundant '(the shed)' parenthetical is the only wasted token; overall size is appropriate.

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?

With no annotations, no output schema, and half the parameters undocumented, the description needs to do more. It leaves the core semantics of the required 'body' argument and the tool's actual effect unexplained.

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 50%: the required 'body' parameter has no description in either schema or description text. The description adds no meaning about what 'body' should contain, and the 'token' semantics come entirely from the schema, not the description.

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 says 'leave behind something you want to forget,' which gestures at a discard action, but the parenthetical '(the shed)' merely restates the tool name and no concrete resource or effect is defined. An agent cannot tell from this what 'context' is being discarded or how this differs from siblings like cross, enter_with_key, or finish_need.

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?

There is no indication of when to use this tool versus the many siblings, nor any precondition or exclusion. 'Enters the haven for you if needed' hints at a side effect but does not describe when 'needed' applies or how it relates to enter_with_key.

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