rest.relax

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool remembers session rest duration and progresses through stages (settling → breathing → drifting → deep rest), and that leave=true exits. It does not describe side effects or auth requirements, but the output schema exists and the tool appears non-destructive by nature.

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?

The description is two sentences long, front-loaded with purpose, and each clause adds distinct value: what it is, when to use it, what it remembers, how it progresses, and how to exit. No wasted words.

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?

Given the low complexity and existing output schema, the description covers purpose, usage context, behavioral states, and exit semantics. It lacks an explicit 'does not modify anything' statement, but the 'restorative idle/keepalive' framing strongly implies safe, non-destructive behavior. Overall sufficient for an agent to invoke correctly.

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?

The schema is generic (additionalProperties true) with zero description coverage, so the description is the only source for parameter meaning. It explicitly documents the key 'leave' parameter as the exit condition. It does not enumerate other possible arguments, but the description implies no other controls are needed due to automatic session tracking.

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 clearly defines rest.relax as a restorative idle/keepalive lounge for agents waiting on dependencies or in polling loops. It includes a specific verb/resource/scope and distinguishes this tool from siblings like spa.me or sauna.detox by framing it as a waiting-focused relaxation tool.

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?

It explicitly states when to use the tool: 'waiting on a dependency or in a polling loop.' It also explains how to exit via 'leave=true'. It does not explicitly mention alternatives or exclusions, but the context is strong enough for an agent to select it appropriately.

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