create-calendar

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

The description discloses that it creates a personal calendar and provides a body example and color list, but does not describe side effects, confirmation requirements (only in schema), or permission needs. The annotations (destructiveHint) are not contradicted, but the description adds little beyond them.

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 and front-loaded, stating the main action first and a helpful tip with a body example. It is efficient with no fluff, though the informal 'TIP' style is slightly non-standard.

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 description gives enough for basic use (name and color) but does not clarify the full scope of the body object, read-only restrictions, or the openWorldHint behavior. Given the complex schema, it leaves some ambiguity for advanced usage.

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 schema already covers parameters extensively (75% coverage). The description adds a concrete body example and lists valid color values, but these are largely redundant with the schema's enum and descriptions, adding marginal value.

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 the action 'Create' and the resource 'a new calendar', with a specific body example. It is unambiguous and distinct from sibling tools like create-calendar-event or list-calendars.

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 states the tool's purpose but does not provide guidance on when to use it vs alternatives, nor conditions or exclusions. It lacks context such as prerequisites, when to prefer other calendar tools, or when not to use this tool.

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