calendars_create_appointment

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, etc.), the description discloses nothing about side effects, required permissions, or idempotency. For a creation tool, critical behavioral context like validation rules, automations triggering, or slot availability checks are entirely absent.

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 extremely under-specified, not concise. While brevity is beneficial, a two-word tautology fails to convey any useful intent or usage context, making it insufficient for an agent to act correctly.

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 17 parameters, no output schema, and a mutating operation, the description is grossly incomplete. It provides no info about required context (e.g., how to obtain calendarId/contactId, time format, recurrence, or concurrency rules), leaving the agent without essential guidance.

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 94%, so the schema provides robust parameter documentation. The description adds no parameter information, but per the baseline for high coverage, this is acceptable; however, it does not compensate for any gaps the schema might have.

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 'Create appointment' is a pure tautology, restating the tool name without any additional specificity. It does not distinguish from siblings like calendars_edit_appointment or calendars_get_appointment, offering no unique resource scope or behavior.

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?

There is no guidance on when to use this tool versus alternatives. No context about prerequisites, selection criteria, or exclusions is provided, leaving the agent to infer entirely from the name.

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