timetree_delete_event_comment

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

With no annotations provided, the description carries the full burden. It does state that this is a destructive delete and requires confirm=true, which is useful safety context. It stops short of explaining side effects, permission needs, or irreversibility beyond the confirmation requirement.

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 short sentences with no filler. The operation is stated first, and the critical confirmation requirement is presented prominently.

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 straightforward delete operation, the description is near-adequate. The required identifiers are discoverable from the schema property names, and confirm's role is clear. It would be more complete if it noted how to obtain the event_uuid and comment_id via sibling tools, but that is not essential for basic usage.

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 only 25%, so the description needed to compensate for calendar_id, event_uuid, and comment_id. It does not explain any of those identifiers. The confirm parameter is repeated in the schema already with the const:true, so the description adds no parameter semantics.

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 resource ('a TimeTree event comment') and the action ('Delete'), so the agent knows what operation this tool performs. It does not explicitly differentiate from sibling tools like timetree_delete_event or timetree_update_event_comment, but the resource is specific enough to avoid obvious confusion.

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 gives no guidance about when this tool should be used versus alternatives, and it does not mention exclusions or preconditions. The only usage hint is 'Requires confirm=true,' which is more of a safety requirement than a usage rule.

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