preview_delete_personal_calendar_event

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

Annotations already declare readOnlyHint=true and destructiveHint=false, aligning with 'no lo borra'. The description adds value by specifying what is verified (owner and scope), providing behavioral detail beyond the annotation flags.

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?

One concise sentence with no fluff. It front-loads the purpose and the non-destructive nature. It could benefit from slightly more structure (e.g., listing parameters), but it is appropriately brief for a simple preview tool.

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 omits return value details and parameter semantics. For a preview tool, the agent needs to know what the verification result looks like (e.g., success/failure, reasons) and how to use the scope parameter. Given the lack of output schema and param coverage, this is a significant gap.

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 0%, so the description must explain the parameters. It does not mention event_id or scope at all, leaving the agent to guess their roles. The description only references 'propietario y alcance' conceptually but does not map them to the 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 the action: 'Verifica propietario y alcance antes de borrar un evento personal' (verifies owner and scope before deleting a personal event) and explicitly clarifies it does not delete ('no lo borra'). This distinguishes it from the sibling 'delete_personal_calendar_event' and other preview tools.

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 gives context: use this tool before deleting a personal event to verify ownership and scope. It implies the workflow of preview-then-execute, consistent with the sibling naming pattern, but does not explicitly mention alternatives or when not to use it. Still, the usage intent is clear.

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