delete_sync_rule

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

Annotations already declare destructiveHint: true and readOnlyHint: false. The description adds meaningful beyond-annotation context: mirrored events are cleaned up afterward by Kalendia, and the operation is irreversible. These details are not present in the structured hints and help the agent understand side effects.

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 with no wasted words. The first sentence states the action, the second highlights consequences. Every clause adds value, and the sentence ordering front-loads the primary purpose.

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?

For a deletion tool with an output schema available, the description covers the essential aspects: the action, the source of the ID, the cleanup side effect, and irreversibility. No critical information is missing for successful invocation.

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 only provides an integer rule_id with no description. The description compensates by linking rule_id to list_sync_rules, giving it semantic meaning and source. While it does not elaborate on constraints or format, this is a significant addition given 0% schema coverage.

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 opens with 'Delete a sync rule,' a specific verb and resource. It also adds a distinguishing scope ('sync rule') and a key behavioral note about mirrored events being cleaned up, which clearly differentiates this from sibling deletion tools like delete_scheduling_page.

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 states 'rule_id from list_sync_rules,' telling the agent where to obtain the required identifier. It also warns that the operation 'cannot be undone,' providing important caution. However, it does not explicitly mention alternatives or when not to use this tool, though the guidance is clear enough.

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