delete_life_event

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. A delete operation is inherently destructive, but the description doesn't specify whether deletion is permanent, whether relations or tags associated with the event are also removed, or whether the operation can be undone. This is a meaningful gap for a destructive mutation tool.

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 concise sentence with zero wasted words. It is appropriately terse for a tool whose semantics are largely captured by its name and schema. However, the extreme brevity leaves out behavioral nuance that could have been included without bloat.

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 single-parameter destructive operation with no annotations and no output schema, the description relies entirely on the name for context. It fails to disclose whether this is a permanent/irreversible action, whether it affects related entities (tags, relations, custom entries), or any required permissions. Given the destructive nature, this is insufficiently contextualized.

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%, with the single id parameter documented as 'エントリID (UUID)'. The description adds no parameter information beyond what the schema already provides. With full schema coverage, baseline 3 applies. The description does not clarify what entity type the UUID refers to, but this is reasonably implied by the life event context.

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 "ライフイベントを削除" (Delete life event) states a clear verb+resource: deletion of a life event. It distinguishes from siblings like update_life_event and list_life_events, but among the many delete_* tools (delete_hobby, delete_custom_entry, etc.) it doesn't add differentiating detail about what a life event specifically is.

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. It doesn't mention prerequisites or exclusions (e.g., whether deleting a life event cascades to related entries, whether it's destructive in a way requiring confirmation). No when-to-use or when-not-to-use context is provided.

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