soundiiz_sync_delete

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

Discloses two-step destructive process and confirms re-call requirement. No annotations exist, so description carries full burden and does so thoroughly, including a skip mechanism.

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?

Two sentences, no redundancy, front-loaded with purpose. Every sentence provides critical operational detail.

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?

Covers the essential two-step behavior and skip option. No output schema, but description mentions return of confirmId. Could detail success response but adequate for a delete operation.

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 coverage is 0%, but description implies usage of id and confirmId. It explains the role of confirmId in the second call but does not elaborate on the id parameter. Adds value beyond schema structure.

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 'Delete a Soundiiz sync' with a specific verb and resource. It distinguishes from sibling tools like soundiiz_sync_get or soundiiz_sync_trigger, which handle different operations.

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?

Provides explicit usage instructions: first call returns confirmId, second call with confirmId executes. Mentions option to skip confirmation via writes.confirmDestructive=false. No explicit alternatives or when-not-to-use, but context is sufficient.

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