create_appointment

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

With no annotations, the description carries the full burden of behavioral disclosure, but it merely states the action without explaining side effects, required permissions, or the impact of parameters like toNotify. It does not mention whether notifications are sent, whether the appointment is linked to a contact, or any other consequences beyond the obvious creation.

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 a single sentence and is free of fluff, but it is too minimal to be considered well-structured for a tool with 11 parameters. It essentially restates the tool name and provides no additional context, so while it is concise, it does not fully earn its place as a helpful description.

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 mutation tool with no annotations and no output schema, the description should at least mention return values, side effects, or prerequisites. It does none of these, leaving gaps around what happens after creation and what conditions must be met. The complexity (11 parameters, enums, required fields) demands more context than a single generic sentence.

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 all 11 parameters are already documented in the schema. The description adds no parameter-specific meaning, but the baseline of 3 applies since the schema does the heavy lifting. No extra credit is earned, nor is any deduction warranted.

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 uses the specific verb 'Create' and clarifies the resource as 'appointment/calendar event', clearly distinguishing it from sibling tools like create_task and create_conversation. It leaves no ambiguity about what action is performed on which resource.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools like get_free_slots, update_appointment, or delete_appointment, nor does it state any prerequisites or exclusions. The agent is left without context for the appropriate invocation scenario.

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