vibo_delete_song_comment

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

Annotations declare readOnlyHint=false, consistent with mutation. The description adds 'Confirm-gated', disclosing that confirm=true is required and without it a preview is returned. This is beyond annotations. However, it does not detail error cases, permissions, or side effects of deletion.

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, front-loaded with purpose, and every word earns its place. There is no redundancy or fluff.

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?

While the confirm-gating behavior is explained, the description lacks information about return values (e.g., success message, preview structure) and prerequisites (e.g., ownership or permissions). Given no output schema, this is a moderate gap for a 5-parameter mutation 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?

Schema description coverage is 100%, meeting the baseline. The description's 'Confirm-gated' echoes the confirm parameter's description, adding marginal value. No additional semantic context is provided for other 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 'Delete a comment on a song', specifying the verb (delete) and resource (comment on song). It distinguishes from sibling tools like vibo_delete_section_comment (deletes section comments) and vibo_comment_on_song (adds comments). The purpose is unambiguous.

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 mentions 'Confirm-gated', which indicates the need for confirm=true, but does not explicitly state when to use this tool vs alternatives like vibo_delete_section_comment. No guidance on prerequisites or when not to use it is provided.

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