Delete label

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

Annotations already signal destructive and idempotent behavior. The description adds useful beyond-annotation context by revealing the cascade effect: deleting the label removes it from associated posts or media rather than deleting those posts/media. No contradiction with annotations.

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 short sentences that are front-loaded: the primary action and scope appear first, and the usage guidance follows. There is no filler or redundant elaboration.

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 one-parameter delete operation, the description covers the action, the cascade effect, and the triggering user intent. It doesn't discuss permissions or response behavior, but the annotations and simple schema make the tool easy to invoke correctly without those details.

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 already provides 100% coverage for the single parameter, labelId, with type and description. The description's 'by ID' phrase reinforces this but adds no new semantic detail beyond the schema.

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?

Clearly states the action ('Delete'), the target ('label by ID'), and the operational effect ('removes the label from all associated posts or media'). This distinguishes it from sibling tools like delete_post, delete_media, and delete_rss_feed, which target different resources.

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 context: 'Use this when the user wants to delete a label.' It does not spell out when not to use this tool or how it differs from update_label/list_labels, but for a simple delete operation the stated intent is sufficient.

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