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

Annotations already declare readOnly=false, destructive=false, openWorld=true, idempotent=false, so the safety profile is covered. The description adds value beyond them by disclosing that attendees may be notified by Freshsales (a side effect not captured anywhere else) and by naming the underlying POST endpoint. It stops short of saying whether notification can be suppressed or what is returned.

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?

A single dense sentence front-loads the operation, its required temporal fields, and its optional attachments, followed by a short endpoint note. Nothing is padded or repeated.

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?

With 10 parameters fully described in the schema and no output schema, the description only needs to frame intent and side effects, which it largely does. The gap is the attendee notification behavior: it says notification may happen but not whether the caller controls it, which matters for a scheduling write.

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%, so every parameter including target_type's enum and the ISO 8601 date formats is documented in the schema itself. The description only restates the headline structure (start/end, optional contact/account/deal attachment, attendees) without adding format or constraint detail. Baseline 3 applies.

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 names a specific verb and resource (create an appointment/meeting) and enumerates its shape: start, end, optional attachment, attendees. The 'WRITE:' prefix also signals its class of operation. It does not explicitly contrast with the other create_* siblings, but the resource distinction is unambiguous.

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?

Usage is implied — create this when you need to schedule a meeting on the calendar with a time range. There is no explicit statement of when to prefer it over freshsales_create_task or freshsales_create_note (e.g. meetings vs. to-dos), and no prerequisites or exclusions are given.

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