skylight_uncomplete_chore

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

No annotations provided, so description carries full burden. It states the tool 'reopens' a chore, indicating status change, but does not mention side effects, permissions, error states, or behavior for non-recurring chores when instance_date is omitted. Some behavioral context but not comprehensive.

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?

Single sentence that front-loads the action and parameters. No redundancy or extra information; every part is necessary.

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 no output schema and no annotations, the description covers the core functionality and optional parameters for recurring chores. However, it lacks explanation of frameId, behavior for recurring chores without instance_date, and error/success outcomes. Adequate but with clear gaps.

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 50%, with descriptions for instance_date and instance_time. The description adds meaning by explaining that instance_date is for reopening a single recurring occurrence. However, id and frameId lack descriptions both in schema and description. Overall, adds some value beyond schema but doesn't fully compensate for gaps.

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?

Description clearly uses verb 'Reopen' and resource 'chore', and distinguishes between a single chore and an occurrence of a recurring chore by mentioning instance_date. It is distinct from sibling tools like skylight_complete_chore and skylight_complete_chore_instance.

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?

Description implies usage for reverting a completed chore, but does not explicitly state when to use this over alternatives such as skylight_complete_chore or skylight_complete_chore_instance. No exclusions or prerequisites are mentioned.

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