Sleep in Bed

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive world interaction. The description adds valuable context about time-of-day constraints, safety checks, and explicit error conditions, going beyond the structured metadata.

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 compact, using two sentences for the main behavior and a concise return/errors list. Every sentence adds meaningful information without redundancy.

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 lack of output schema and parameter descriptions, the description covers the essential behavior, conditions, return format, and error cases. It does not fully detail edge cases like occupied beds or exact coordinate semantics, but it is substantially complete for a tool of this complexity.

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?

With 0% schema description coverage, the description partially compensates by explaining that coordinates are optional and used to target a specific bed instead of the nearest one. However, it does not clarify whether partial coordinate triples are allowed or the exact meaning of numeric values.

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 states the tool's action: finding the nearest bed (or at given coordinates) and sleeping in it. This specific verb+resource distinguishes it from all sibling tools, none of which overlap with sleeping.

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 the tool works (night/thunderstorms) and necessary conditions (bed safe, no monsters). While it doesn't mention alternatives, there is no other sleep tool among siblings, so the context is sufficient.

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