Create Appointment Group

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

Annotations already include openWorldHint=true and destructiveHint=true, so the description doesn't need to restate side effects. It adds useful context about appointment groups being sign-up slots and how to structure time slots. However, it doesn't clarify what 'destructive' entails in this creation context, which would be helpful given the annotation.

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?

Two sentences, front-loaded with purpose, no filler. Every clause earns its place by providing necessary usage details.

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 tool has 11 parameters, no output schema, and a non-trivial creation workflow. The description covers the essential requirements and the most important data structure (new_appointments). While it doesn't mention return values or optional settings like participant_type, the rich schema and annotations mitigate these gaps.

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 baseline is 3. The description adds value by mandating 'at least one' context_code (not encoded in schema) and clarifying the new_appointments structure, complementing the schema descriptions rather than merely repeating them.

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?

Description states a specific verb ('Create') and resource ('new appointment group (sign-up slots) in Canvas Scheduler'), immediately distinguishing it from sibling tools like update_appointment_group, delete_appointment_group, and list_appointment_groups. It is clear and not tautological.

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?

Provides explicit guidance on required inputs ('Provide at least one context_code... and a title') and explains the format for new_appointments. While it doesn't mention alternatives or exclusion scenarios, the context is clear enough for an agent to know when to use it.

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