Chore Execute Tool

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly states that the tool records an execution and advances the next scheduled time, which makes the mutation effect clear. It does not mention permissions or reversibility, but the core behavioral consequence is adequately disclosed.

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 two short sentences with no filler. The primary action is front-loaded, and the second sentence adds meaningful behavioral context about execution recording and schedule advancement.

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?

For a two-parameter tool with fully documented schema and an output schema, this description is sufficient. It tells the agent what the tool does and what side effect to expect, and the schema supplies the remaining invocation details.

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 100%, so the input schema already documents both parameters: 'chore' as name or ID and 'done_by' as an optional user ID. The description adds no additional parameter-specific meaning, so it rests at the baseline for high schema coverage.

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 'Mark' and resource 'chore', clearly stating the action: 'Mark a chore as done.' The second sentence adds the operational effect—recording an execution and advancing the schedule—which further distinguishes it from siblings like chore_undo_tool or chores_list_tool.

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 intended usage is implied: use this when a chore has been completedsomeone, since it 'records an execution and advances the next scheduled time.' However, there is no explicit guidance about when not to use it or how it compares to related tools like chore_undo_tool or task_complete_tool.

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