convert_chore_to_subtask

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

The description explicitly states that the original chore is deleted and a subtask is created, which are key behavioral traits. However, with no annotations provided, it could disclose more: whether the operation is reversible, if permissions are required, or what happens to subtasks of the original chore.

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 sentence that efficiently conveys the action and side effects. No redundant information.

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 main operation but lacks details on edge cases (e.g., what if target is the same as source, what happens to existing subtasks of source). It is adequate for a simple operation but not fully comprehensive.

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 100%, with each parameter having a descriptive comment. The description adds minimal extra value beyond the schema. Baseline 3 is appropriate.

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 specific action: convert a standalone chore into a subtask. It defines the resource (chore), the transformation (subtask), and the side effects (deletes original). This distinguishes it from sibling tools like create_subtask (which doesn't delete) and delete_chore (which only deletes).

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?

No guidance on when to use this tool versus alternatives such as create_subtask or delete_chore. The description does not specify prerequisites (e.g., source must be a standalone chore) or scenarios where this tool is inappropriate.

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