createAppointment

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

With no annotations, the description carries the full burden. It discloses platform-specific naming conventions that prevent errors and clarifies the invitees structure. However, it does not mention side effects, permission requirements, or return behavior, leaving significant gaps.

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 entire description is a single well-structured sentence. It is front-loaded with the core purpose and immediately provides the most important usage caveats. No redundant information.

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 10-parameter create tool with no output schema, the description covers the most error-prone naming conventions but omits return value, permissions, and error behavior. It is adequate for basic usage but not fully complete for an agent to invoke confidently in all contexts.

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 high (90%), so baseline is 3. The description adds value by warning against incorrect field names (startTime/endTime, appointmentTypeId/appointmentOutcomeId) and reiterating the invitees shape. It does not address the one undocumented parameter (allDay) or provide deeper semantics beyond what the schema already offers.

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 clearly states 'Create an appointment' with a specific verb and resource. It also provides critical naming conventions (start/end, typeId/outcomeId, invitees format) that distinguish this tool from similar create tools and prevent common mistakes.

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?

No explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions or alternative tools to prefer in certain scenarios. The naming hints are about parameter usage, not tool selection.

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