delete-my-calendar-permission

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

The annotations already indicate destructiveHint=true (mutation) and readOnlyHint=false. The description adds that the action revokes access and that certain permissions cannot be deleted. It does not contradict annotations. However, it could mention that the deletion is irreversible or that owner-level permissions may be needed.

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 two sentences and a tip, which is concise. The action is front-loaded. The tip uses a bullet point for clarity. It could be slightly more structured, but it is efficient without unnecessary words.

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 the tool's complexity (a simple delete with one required parameter) and the presence of annotations (destructiveHint) and a note about limitations, the description is fairly complete. It lacks details about response format, but since there is no output schema and it's a delete, that is acceptable.

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 input schema has 4 parameters with 100% description coverage, so the schema already documents them. The description does not add any additional meaning beyond what is in the schema, scoring a baseline 3.

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 states 'Delete navigation property calendarPermissions for me' and the tip clarifies it revokes a calendar share or delegate access. The purpose is clear, though the first line uses technical phrasing that may not be instantly understood. It distinguishes itself from siblings like delete-drive-item-permission by focusing on calendar permissions.

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 tip explicitly says when to use the tool ('revokes a calendar share or delegate access') and provides a prerequisite (get permission id via list-my-calendar-permissions). It also warns about non-removable permissions (isRemovable=false) and the resulting error, which helps the agent avoid misuse. This is excellent guidance.

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