skylight_delete_source_calendar

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds context about what is removed ('connected source calendar, incl. webcal subscriptions') but does not disclose cascading effects, reversibility, permissions, or post-deletion behavior, which would add further value.

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 a single, front-loaded sentence with no filler. It conveys the essential purpose efficiently and earns its place.

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?

Although the purpose is clear, the description omits details about frameId, what happens after deletion, and what the response looks like (no output schema exists). The annotations cover the destructive safety profile, but an agent still lacks enough context to confidently handle the optional frameId parameter or know the outcome.

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 0%, so the description had to explain what 'id' and 'frameId' mean. It does neither; it only states the operation. The agent is left guessing what frameId refers to and what values are expected.

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 names a specific verb ('Remove') and resource ('connected source calendar') and explicitly includes webcal subscriptions, which distinguishes it from generic delete tools. The resource type is precise enough that an agent can tell it apart from other calendar tools like skylight_update_calendar or skylight_categorize_source_calendar.

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?

Usage is implied: use this tool when removing a connected source calendar or webcal subscription. However, it does not explicitly state when not to use it or compare it with related alternatives such as updating, categorizing, or unlinking calendars.

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