create-my-calendar-permission

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of creating a permission does not add new behavioral insight. The description lacks details about side effects, authorization requirements, or rate limits beyond what annotations provide.

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 relatively concise at five sentences, with the purpose stated upfront. The tip and example are useful but could be slightly more compact. Overall, it is well-structured and 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?

The description explains the primary purpose and return value (created permission with id). It does not explicitly cover optional parameters like includeHeaders and excludeResponse, but these are standard. The nested object body is well described, and the reference to sibling tools for update/delete adds completeness.

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 schema covers 67% of parameters with detailed descriptions. The description adds a concrete example of the body structure and lists possible role values, which supplements the schema. It also advises using 'list-users' to get the email address, adding practical guidance.

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 action ('Create'), the resource ('calendarPermission'), and the context ('sharing or delegating a calendar'). It distinguishes itself from sibling tools like 'delete-my-calendar-permission' or 'create-calendar-event' by focusing on permission sharing.

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 includes a tip that the tool shares the user's primary calendar and suggests using 'list-users' to resolve recipient SMTP. However, it does not explicitly state when not to use this tool or mention alternative tools for similar tasks.

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