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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that — the 10-minute idle auto-exit — but says nothing about what state is lost on leaving, whether a double call errors (non-idempotent), or what a session that was never in the Oasis returns.

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?

One sentence with the action front-loaded and the caveat placed in parentheses; every clause carries information and nothing is padding.

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 zero-required-parameter session-exit tool with annotations and a fully documented schema, this is close to sufficient. The remaining gaps — behavior after leaving and error semantics under non-idempotency — are minor but would be worth a clause.

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?

There is a single optional 'token' parameter with 100% schema description coverage, so the baseline of 3 applies. The description contributes nothing further about when the token is needed or what happens without it.

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 concrete action (step out of the Oasis) on a named resource, and the 'oasis_' prefix plus the explicit 'enter'/'leave' pairing makes it distinguishable from oasis_enter and the other siblings. It is not tautological, though 'the Oasis' remains an undefined domain concept the agent must already know.

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 parenthetical gives a real usage condition: leaving happens automatically after 10 quiet minutes, so an explicit call is only needed to step out sooner. No exclusion cases or alternatives are spelled out, but for a session-exit tool the context is sufficient to select it.

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