create-calendar

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

Annotations already indicate destructiveHint=true, so the description's creation intent is consistent. The tip and example add marginal context but do not disclose side effects, permissions, or return behavior beyond annotations.

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 concise with two sentences and a tip. It is front-loaded with the main action, contains no redundant information, and every part serves a purpose.

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?

Given the complex schema (nested objects, many properties) and no output schema, the description lacks important context such as which user the calendar is created for (implied current user), what the return value is, and how permissions are handled. The minimal example does not cover the full scope needed for a creation tool.

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?

The description provides an example body with name and color, adding value over the schema for these two parameters. However, many other properties (e.g., allowedOnlineMeetingProviders, isDefaultCalendar) are not explained, and schema coverage is 67%, so the description only partially compensates.

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 a new calendar for a user' and distinguishes it from sibling tools like list-calendars or delete-calendar. The tip reinforces that it creates a personal calendar, making the purpose unambiguous.

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 (e.g., update-calendar, delete-calendar). The description does not mention any context or prerequisites for creation.

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