Delete Chore

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

With no annotations, the description carries the burden of exposing destructive behavior. It clearly states the deletion is permanent and adds the creator-only authorization rule. It could mention what happens to associated data or history, but it is reasonable for a simple delete.

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, focused sentences with the core action front-loaded and no redundant details. Every word 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?

Given the tool's simplicity, one required parameter, and existing output schema, the description fully covers the core semantics: what is deleted, whether it is reversible, and who is authorized to do it.

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 schema already describes chore_id as 'The ID of the chore to delete.' The description adds no extra parameter-level meaning, and with 100% schema coverage, it doesn't need to do much more.

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?

States the exact operation: 'Delete a chore permanently.' and names the resource. This clearly distinguishes it from siblings like archive_chore, pause_chore, complete_chore, and update_chore.

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?

Provides clear context about who may use the tool: 'Only the chore creator can delete a chore.' It does not explicitly mention alternatives such as archiving a chore, so it slightly misses full when-not guidance.

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