Float tank

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

With no annotations, the description carries the full burden. It discloses the experience as quiet and low-stimulus, which is a behavioral trait. However, it does not mention the duration constraint (0–30s) and even says 'a minute', which conflicts with the schema and could mislead about the session's length. It also lacks details about effects or state changes.

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 extremely concise—two short sentences—and front-loads the core idea ('Sensory deprivation') followed by a qualitative and usage note. Every word earns its place without unnecessary elaboration.

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 simple tool with one optional parameter and no output schema, the description gives the core experience and a usage pairing, but it does not explain the exact duration dependency or clarify the outcome of the session. The inconsistency between 'minute' and the 30-second maximum also leaves ambiguity, making the description partially complete.

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 description covers 100% of the parameter, so the baseline is 3, but the description's 'a minute' conflicts with the parameter's maximum of 30 seconds. This actively misleads an agent about a valid value for 'seconds', thus detracting from parameter understanding.

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 identifies the tool as 'sensory deprivation' with a 'quiet, low-stimulus minute', which clearly conveys the purpose of a float tank. It distinguishes from siblings like sauna and cold_plunge by emphasizing low-stimulus, and the pairing hint with 'breathe' adds context. However, it lacks an explicit verb like 'perform' or 'float in', so it is not maximally explicit.

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 phrase 'Pairs well after breathe' explicitly recommends using this tool after the 'breathe' tool, which is a sibling, giving a clear contextual usage. It does not mention when to avoid or alternative tools, but the pairing instruction is a concrete guideline.

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