delete_chore

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

With no annotations, the description fully discloses the destructive nature ('permanently'), authorization requirement ('only chore creator'), and return value ('confirmation of deletion'). This is sufficient for a simple delete operation.

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 sentences, no unnecessary words, critical information front-loaded. Perfectly concise.

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 all core aspects: action, permanence, authorization, and return. While it could mention error cases (e.g., chore not found), it is adequate for a simple tool without output schema or annotations.

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 single parameter 'chore_id' is fully described in the schema. The description adds no further semantic meaning beyond what the schema already provides, which meets the baseline for 100% 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 clearly states the verb 'Delete' and the resource 'a chore', and specifies 'permanently' to indicate irreversibility. It effectively distinguishes from sibling tools like complete_chore (mark complete) or update_chore (modify fields).

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 note 'Only the chore creator can delete a chore' provides a key usage constraint. However, it lacks explicit comparison to alternatives like skip_chore or update_chore to explain when deletion is appropriate versus other modifications.

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