create-calendar

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

Annotations already indicate destructiveHint=true, so the description's claim of 'creates' is consistent. However, the description does not disclose additional behavioral traits such as whether the calendar is automatically shared, permission requirements, or error conditions. It adds minimal value 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 short with two sentences and a tip, making it efficient. It front-loads the purpose and provides a quick reference. However, the tip formatting is slightly messy and could be more structured.

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 complexity of the input schema (many properties, nested objects) and no output schema, the description is incomplete. It does not explain what the tool returns, how to handle required fields, or the significance of the many optional parameters. It falls short of being fully informative.

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 a minimal example with name and color and lists available colors, which adds some meaning beyond the schema. However, the schema has 67% description coverage, so the schema already documents many parameters. The description does not explain other parameters like owner or permissions, leaving gaps.

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 specifies it creates a personal calendar. This distinguishes it from sibling tools like create-calendar-event which create events, not calendars. However, it does not explicitly differentiate from other calendar creation tools, but the verb and resource are specific.

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 prerequisites, context, or exclusions. The tip offers a minimal example but no usage scenarios or restrictions.

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