sleep_delete_sleep

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 explicitly states that the action is permanent, which is a critical behavioral trait for a delete operation. It does not mention other side effects, but the permanence disclosure is sufficient for this simple mutation.

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 short sentences with no wasted words. It front-loads the action and immediately follows with the key behavioral trait. Extremely efficient.

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 simplicity of the operation (one required integer parameter) and the presence of an output schema, the description covers everything an agent needs to call it correctly: what it does, the permanence, and the parameter is already documented in the schema.

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 already provides a clear description for sleep_id ('ID of the sleep record to permanently delete'), so the description does not add meaning beyond the schema. With 100% schema coverage, the baseline of 3 is appropriate; the description merely reinforces the permanence.

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 the exact action ('Delete a sleep record') with a specific resource. It clearly distinguishes from sibling tools like sleep_create_sleep and sleep_update_sleep by naming the delete operation. No ambiguity.

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 implies when to use it (to remove a sleep record) but provides no explicit guidance on when not to use it or when an alternative like update would be more appropriate. It does not mention any prerequisites or exclusions.

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