Add chore

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

The description adds some behavior beyond the annotations: it notes optional assignment, repeating cadence, and the title requirement. However, it omits important behavioral details already present in the schema, such as dry_run returning a preview without writing, idempotency semantics, and audit/policy implications of the member field.

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?

Two short, front-loaded sentences with no filler. The first sentence states the core action and main options, and the second calls out the required input, so every sentence earns its place.

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 plus a fully documented schema and an output schema provide enough to invoke the tool mechanically. It is incomplete in guiding tool selection and in surfacing dry_run/idempotency behavior, but the parameter-level details are already covered elsewhere.

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%, so the parameters are fully documented in the schema itself. The description echoes title, assignment, and repetition but adds no semantic detail beyond what the schema descriptions already provide, making the baseline 3 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 a specific verb and resource: 'Adds a chore'. It also conveys key options (assign, repeat), but it does not explicitly distinguish this creation tool from sibling assign_chore, which is the only real overlap risk.

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 is given about when to use add_chore versus assign_chore, complete_chore, or rotate_chores. The phrase 'optionally assigned to someone' implies overlap with assign_chore but never clarifies the boundary or suggests an alternative.

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