notion_create_appointment

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

Beyond the annotations (readOnly=false, idempotent=false), the description reveals the duplicate-prevention behavior around gcal_event_id and warns against reusing it for from-scratch creations. It also discloses the return shape. It does not discuss permissions or rate limits, but for a create operation this is solid behavioral context.

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 front-loaded with purpose, followed by high-value usage conditions, then a compact parameter breakdown and return note. No sentence is redundant; the Args section earns its place given the low schema coverage signal.

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?

The description covers creation scope, GCal sync behavior, recurrence, parameter semantics, and return value. It doesn't explicitly list which parameters are required, but the schema does; given the tool's complexity and available output schema, this is complete enough.

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?

Although the context signal reports 0% schema coverage, the Args section enumerates every parameter with meaningful semantics: which fields are optional, which are for GCal sync, and what the recurrence types are. This fully compensates for the reported schema gap.

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 opening sentence names a specific action ('Create') and resource ('Appointment in the Notion Appointments database'), immediately distinguishing it from siblings like notion_update_appointment or notion_get_appointments. The rest of the description reinforces this create-only scope.

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?

It explicitly contrasts the two creation contexts: syncing from Google Calendar (pass gcal_event_id) versus creating from scratch (omit it and call gcal_create_event separately). This directly tells an agent when to use this tool and when to delegate to a sibling.

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