skylight_delete_chore

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

With destructiveHint=true already present, the description adds meaningful behavioral context by clarifying that deletion can target a single occurrence or the whole series. It is consistent with the annotation and adds nuance beyond it.

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?

A single short sentence with no wasted words. The core action is front-loaded and the optional scope is expressed efficiently.

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 description is adequate for a basic destructive tool but leaves gaps: it does not mention the confirm/preview behavior, frameId semantics, or how non-recurring chores behave. The schema fills some of this, but the description alone is lean for a 4-parameter destructive operation with no output 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?

Schema description coverage is only 50%, leaving id and frameId undocumented. The description restates the occurrence-vs-series choice already present in apply_to's schema description, but it does not add meaning for the undocumented params, and with low coverage the description needed to compensate.

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 operation ('Delete') and resource ('a chore'), and adds a scope nuance ('optionally a single occurrence or the whole series'). This clearly distinguishes it from sibling delete tools for other resources.

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?

Usage is implied by the verb and resource name, but the description gives no explicit guidance on when to choose this over alternatives such as completing, updating, or uncompleting a chore. There are no exclusions or alternative tool mentions.

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