bed-sleep

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the two main behaviors: skipping the night and setting the spawn point. It does not mention failure conditions or prerequisites, but for a simple action this is reasonably transparent.

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 a single sentence that is concise and front-loaded with the key verb and resource. Every word contributes to meaning without redundancy or unnecessary detail.

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 tool's simplicity, the description adequately explains its purpose and effects. It does not describe return values, but no output schema exists and the action is straightforward. The main gap is lack of mention of potential failure conditions, but this is a minor omission for a 3-param action.

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 100% with each parameter (x, y, z) having a basic description like 'X coordinate'. The tool description does not add additional meaning to the parameters, but since the schema already describes them adequately, the baseline score of 3 is appropriate.

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 action ('Sleep in a bed') with its two primary effects: skipping night and setting spawn point. It distinguishes itself from sibling tools like bed-wake, and is specific about the resource and outcome.

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 description provides clear context for when to use the tool (to skip night and set spawn point). It does not explicitly mention exclusions or alternatives, but the stated purpose serves as a strong usage guideline. Given there are no annotations, this is sufficient.

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