skylight_uncomplete_chore

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

Annotations already indicate this is a non-read-only but non-destructive operation. The description adds useful behavioral context by clarifying that the tool toggles a completed chore back to an opened state and can target one occurrence via instance_date. No contradictions with annotations.

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?

One compact sentence contains the operation, the resource, and the optional occurrence behavior. The parenthetical 'un-complete' clarifies the awkward tool name without adding fluff.

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 covers the core operation and the key occurrence-selection path, but it leaves id and frameId semantics unexplained and does not address how instance_time relates to instance_date. With no output schema, an agent gets the essentials but not the full parameter interaction.

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 documents instance_date and instance_time, with 50% overall coverage. The description adds meaning to instance_date by explaining its role in reopening a single occurrence. However, it does not clarify the required id parameter or frameId, leaving those semantics to inference.

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 ('Reopen (un-complete)') and names the resource ('a chore, or a single occurrence of a recurring chore'). It clearly differentiates from sibling tools like skylight_complete_chore and skylight_complete_chore_instance by being their inverse and by explicitly scoping the operation to either the whole chore or one occurrence.

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 gives an explicit usage condition: pass instance_date to reopen only a single recurring occurrence instead of the whole chore. It does not name alternatives or state when not to use the tool, but the usage context is clear enough relative to the sibling complete/uncomplete tools.

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