delete-my-calendar-permission

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

Annotations already set destructiveHint=true, so destructive nature is clear. The description adds that it revokes share/delegate access and that non-removable permissions will error. This provides useful behavioral context beyond annotations. However, it does not detail the exact side effects (e.g., whether the user is immediately removed from access) or reversibility, which would push to a 5.

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 very concise: one sentence stating the purpose, followed by a short tip. No redundant information. Every sentence adds value, and the main action is front-loaded.

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 there is no output schema, the description covers the essential context: what the tool does, prerequisites (list permissions), constraints (isRemovable=false), and a note about error cases. It could mention the expected response (e.g., 204 No Content) but that is common for delete operations. Overall, it is sufficiently complete for an agent to use correctly.

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?

All 4 parameters have schema descriptions, so baseline is 3. The description does not add significant extra meaning for parameters like If-Match or includeHeaders/excludeResponse. The tip implies that calendarPermissionId is critical, but the schema already requires it. No additional parameter semantics 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 tool deletes a calendar permission (navigation property calendarPermissions) for the user. The tip explicitly says it revokes a calendar share or delegate access, which is a clear purpose. It is distinct from other delete tools in the sibling list (e.g., delete-calendar, delete-calendar-event) because it specifically targets 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 provides explicit guidance: get the permission id via list-my-calendar-permissions before using this tool, and warns that permissions with isRemovable=false cannot be deleted (Graph returns an error). This tells the agent when to use and when not to use the tool, with a clear alternative (list first).

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