timetree_add_event_comment

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

With no annotations, the description must carry behavioral disclosure. It discloses that this is a real write by requiring confirm=true, which matches the schema const. However, it does not mention whether comments are visible to all calendar members, whether deletion by comment authors is supported, or what happens when the write succeeds or fails.

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?

One short sentence that front-loads the action and then stresses the confirm requirement. Efficient and easy to parse, though it could have included a tiny bit of parameter context without becoming bloated.

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 simple 5-parameter write action, the definition is nearly complete enough to invoke the tool, but an agent might not know how to obtain a valid event_uuid or calendar_id, or what silent affects. The absence of an output schema means the description should hint at return values, but does not. Still, the essential safety-critical confirm parameter is explicit.

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 20%, so the description must compensate for the mostly undocumented parameters. It names the action but does not explain the roles of content (does it support HTML?), event_uuid, calendar_id, or silent. The confirm parameter is described in the schema, so the description adds no extra meaning there.

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 states a clear verb and resource: 'Add a comment to a TimeTree event.' This distinguishes it from the event-level create tool and the list/update/delete comment siblings, though it doesn't name those siblings explicitly.

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 when to use it (when a comment should be added to an event) and emphasizes the confirm=true authorization gate. However, it does not explain how this differs from creating a memo, when to set silent, or what prerequisites (e.g., must already have the event_uuid from a list_events call) are needed.

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