remove_bed

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the bed must be empty and that delete_objects controls whether contained objects are deleted, which signals a destructive side effect. It does not state irreversibility, required permissions, or what happens to the deleted objects.

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?

Two short sentences with zero wasted words. The core operation is front-loaded and the key constraint follows immediately.

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?

The output schema exists, so return values need not be explained. For a destructive two-parameter tool with no annotations and 0% schema coverage, the description gives the essential constraint but leaves gaps around the bed identifier format, permissions, and irreversibility.

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 description coverage is 0%, so the description must compensate. It explains the meaning of delete_objects and its interaction with bed emptiness, but the required 'bed' parameter is only implied as an identifier with no format or accepted values described.

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 states a specific verb and resource: 'Remove a bed.' This clearly identifies the operation and is distinguishable from siblings like set_bed or move_to_bed. However, it does not explicitly differentiate itself from related removal tools such as remove_objects, so it falls short of a 5.

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 sentence 'It must be empty unless delete_objects is true' provides an important precondition and implies when to set delete_objects. But it does not say when to use this tool versus alternatives like remove_objects, nor does it describe failure behavior or prerequisites such as permissions.

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