skylight_delete_source_calendar

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

With no annotations supplied, the description must disclose behavioral traits. It only states the action but does not mention side effects (e.g., cascading deletion of events), irreversibility, or permissions needed. This is insufficient for safe selection.

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 extremely concise (one sentence) and front-loads the action. However, it sacrifices necessary detail, making it borderline under-specified. Conciseness is adequate but not exemplary.

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 no output schema, no annotations, and zero parameter coverage, the description should provide more context about the tool's behavior, return value, and error conditions. It is incomplete for a delete operation that may have significant effects.

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%, meaning the schema adds no meaning to parameters. The description does not elaborate on the purpose of 'id' or 'frameId', leaving the agent to guess. It adds no value beyond the schema.

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 ('Remove') and the resource ('a connected source calendar'), explicitly including webcal subscriptions. This distinguishes it well from sibling tools like skylight_list_source_calendars or skylight_create_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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, disclaimers, or what to check before deletion. A user must infer context from the name alone.

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