delete_event_occurrence_comment

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

The description mentions 'soft-delete', indicating non-destructive behavior, and explains the flexible input format for event_id. However, it does not disclose what happens if no comment exists, error handling, or permission requirements. With no annotations, more detail would be helpful.

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 sentences long, front-loading the core action and then adding detail on event_id. No extraneous information; every sentence contributes value.

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 two required parameters and an output schema, the description covers the basic action and event_id flexibility but omits the return value, missing parameter format for date, and edge cases. It is adequate but not comprehensive.

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 0%, so the description must compensate. It thoroughly explains event_id (accepts various reference forms and resolves to UUID), but only vaguely mentions date as part of the occurrence. The date parameter lacks format or constraints, leaving it partially ambiguous.

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 action: 'Soft-delete the latest comment on an event occurrence (date).' It specifies the verb (soft-delete), resource (latest comment on an event occurrence), and context (occurrence date), distinguishing it from siblings like delete_comment (general) and delete_event_occurrence (deletes occurrence itself).

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 description implies usage for deleting the latest comment on an event occurrence, but does not explicitly compare to alternatives like patch_event_occurrence_comment or delete_comment. No 'when to use' or 'when not to use' guidance is provided.

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