skylight_delete_event

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description's 'Delete' is consistent with that. It adds no additional behavioral context such as permanence, cascading deletes, or permissions, which annotations do not cover.

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. Every word 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?

For a simple two-parameter delete operation, the core invocation is conveyed, and annotations supply the destructive safety signal. However, the optional frameId parameter is left unexplained, and no guidance is given on prerequisites or side effects, making it minimally complete.

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?

With 0% schema description coverage, the description must compensate for both parameters. It clarifies that 'id' identifies the event to delete, but 'frameId' is left entirely unexplained and no relationship between the parameters is described.

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 uses a specific verb and resource ('Delete a calendar event') and the mechanism ('by id'). It clearly differentiates from sibling deletion tools for meals, messages, tasks, rewards, and chores.

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 implies that the tool should be used when an agent has a calendar event id and wants to remove it, but it does not explicitly state prerequisites or when to prefer it over alternatives such as update_event or delete_source_calendar. No misleading guidance is present.

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