update-my-calendar-permission

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

The description discloses that only the role property is writable and lists the allowed enum values. However, there is a contradiction with the 'destructiveHint: true' annotation, as updating a role is not typically destructive. This slightly lowers the score.

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 concise with two clear parts: the initial technical statement and the helpful tip. It is well-structured and contains no unnecessary information.

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 complexity of the input schema (nested object) and lack of output schema, the description adequately explains the key behavioral constraints and provides context for using the tool.

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 description adds value by explaining that only the role property should be included in the body and provides the specific enum values. This goes beyond the schema's descriptions, which cover 75% of parameters.

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 it updates an existing calendar permission, specifying the verb 'changes' and the resource 'calendar permission'. It distinguishes from sibling tools like create-my-calendar-permission and delete-my-calendar-permission by focusing on updating an existing permission.

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 explicitly provides when to use this tool (updating only the role) and when to use alternatives (delete and recreate for changing other properties). It also instructs to get the permission ID via list-my-calendar-permissions.

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