delete_sleep

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

Since no annotations are provided, the description carries the behavioral burden. 'Permanently delete' clearly communicates that the action is irreversible, and the instruction to get interval_id from get_sleep_history adds useful workflow context. It does not discuss permissions or potential cascading effects, but the core destructive behavior is disclosed.

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 no filler or repetition. The key action and prerequisite are front-loaded, making the description highly scannable and 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?

For a simple two-parameter delete tool with no output schema, the description adequately covers what is deleted and how to obtain the needed interval_id. The only notable gap is the purpose of child_uid, but the overall usage workflow is still clear.

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 input schema has 0% description coverage, so the description must compensate. It explains interval_id by telling the user to obtain it from get_sleep_history, but child_uid is left completely unexplained. This is partial compensation only.

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 uses a specific verb 'delete' with a clear resource 'sleep entry' and the word 'Permanently' signals irreversible deletion. It distinguishes this tool from siblings like edit_sleep, delete_diaper, and delete_growth by naming the exact resource.

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 states when to use the tool (to permanently delete a sleep entry) and gives a clear prerequisite: obtain interval_id from get_sleep_history first. It does not explicitly mention when not to use it or alternatives, but the context is clear enough.

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