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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states the destructive scope (calendar and every event), irreversibility, and the need for user confirmation. This is strong transparency for a deletion tool.

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?

Three short sentences, each adding essential information: the action and scope, a key constraint, and a required safety step. No filler or repetition.

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 destructive operation with no output schema and no annotations, the description covers the critical aspects: what is deleted, irreversibility, the default-calendar restriction, and user confirmation. It could mention how to find a calendarId or explicitly point to list_outlook_calendars, but the core calling context is adequately handled.

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 only 50%: mailbox is documented, but calendarId is a bare string with no description. The tool description does not clarify what calendarId should contain or how to obtain it, so the undocumented parameter is left to the agent to infer.

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?

States a specific action and resource: 'Delete a calendar and every event on it.' This clearly distinguishes the tool from delete_outlook_calendar_event and other sibling delete operations.

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?

Provides explicit usage conditions: the default calendar cannot be deleted, the operation is irreversible, and the agent must ask for user confirmation first. It does not name alternative tools, but the 'default calendar cannot be deleted' exclusion and confirmation requirement give clear operational guidance.

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