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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the important disclosure that it "opens nothing by itself" and merely returns UI-level instructions (screens, buttons, fields) that must be enacted through the browser tools. That is genuine context beyond the structured fields. It omits what the returned instruction payload looks like and any prerequisites (e.g., an already-open Cloud Browser session), which matters since there is no output schema.

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 operational content is front-loaded and clear, but the text is padded with low-value material: "from ChatGPT, Claude or any AI agent" and a trailing marketing note that "Intervals.icu's official API: Yes... (checked 6 Nov 2026)" do nothing to help an agent call the tool correctly. Roughly a third of the description is filler that competes with the one sentence that actually matters.

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?

With no parameters and no output schema, the description carries the full burden, and it does explain the deliverable (a step-by-step guide of screens, buttons, and fields) plus the handoff to the browser tools. But it never explains how the tool knows which event is in scope, nor what the response contains structurally. It is adequate to start a call but leaves the agent guessing at the edges.

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 tool takes zero parameters, so the schema-dimension baseline is 4. The description adds nothing here that could be added, and there is no misleading implication about inputs. However, it also never addresses how the target event is identified, which is a real gap for a deletion-shaped task.

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 first sentence names a specific verb and resource ("Delete calendar event in the user's own Intervals.icu account"), and the second sentence corrects the reader's likely assumption by revealing the tool actually returns step-by-step instructions rather than performing a deletion. That correction is valuable, though the initial imperative phrasing fights against the actual behavior and could momentarily mislead. No sibling tool is named for comparison, so differentiation is left implicit.

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?

Gives an explicit workflow: call this first to get the step-by-step procedure, then execute it with the cotlet_browser_* tools in the user's Intervals.icu Cloud Browser. The sequencing and the alternative execution path are clear. It stops short of saying when NOT to use this (e.g., when the user just wants a summary of events, where list_calendar_events applies).

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