skylight_delete_chore

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

No annotations exist, so the description partially compensates by noting the option to delete a single occurrence or the whole series. However, it omits important behavioral details such as permanence, effects on related data, or required permissions.

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, front-loaded sentence that conveys the core purpose efficiently. There is no extraneous text, but it could be slightly more structured to improve readability.

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 has 3 parameters, no output schema, and no annotations, the description is too minimal. It does not explain id or frameId, nor does it describe the response or side effects. A more complete description is needed for a destructive operation.

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 only 33% (only apply_to has a description). The description repeats the apply_to option without adding new insight, and it does not explain id or frameId. With low coverage, the description should compensate but fails to do so.

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 ('Delete a chore') and specifies a key option ('optionally a single occurrence or the whole series'). It distinguishes this from siblings like skylight_complete_chore or skylight_update_chore by focusing on deletion.

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 the tool is for deleting chores but does not explicitly guide when to use it versus related tools (e.g., when to delete vs. complete or uncomplete). No exclusion criteria or alternative suggestions are provided.

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