skylight_set_default_calendar

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

With no annotations, the description carries full burden. It only states a mutation, without disclosing side effects, permissions, reversibility, or impact on existing events. Minimal transparency.

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?

Single sentence with no fluff. Every word serves a purpose. Appropriate length for a simple setter action.

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?

Missing explanation of the frameId parameter and the concept of a 'source calendar' vs 'default'. No mention of prerequisites or related tools. For a simple tool, still incomplete for confident agent 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?

Description adds no extra meaning beyond schema. The 'id' parameter is already described in schema. The 'frameId' parameter is undocumented in both schema and description. Schema coverage is 50% and description does not compensate.

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 provides a specific verb ('Set'), resource ('default source calendar'), and scope ('for new events'), clearly distinguishing this tool from siblings like skylight_update_calendar or skylight_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?

No guidance on when to use this tool vs alternatives such as skylight_update_calendar. Does not mention prerequisites or context (e.g., requiring an existing source calendar).

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