uninstall_sticker_set

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

Annotations already flag readOnlyHint=false, indicating a write operation. The description adds no further behavioral detail (e.g., whether the sticker set remains available for reinstall, or if any confirmation is needed). It does not contradict annotations, so score remains at baseline.

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?

A single, front-loaded sentence that conveys the core action without excess. It is as concise as possible while still being informative.

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?

Given the low complexity (one parameter), presence of annotations, and an output schema, the description covers the essential operation. However, it lacks contextual details like how to obtain a sticker set's short_name, which would make it fully self-contained.

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% and the description does not explain the 'short_name' parameter. It is unclear what format is expected or where to obtain it. With only one required parameter, the description should have provided at least a hint about its semantics, but it does not.

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 (remove/uninstall) and the target resource (sticker set) from the account. It distinguishes from sibling tools like 'install_sticker_set' and 'get_installed_stickers' by its explicit 'remove' semantic.

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 implies use when removing an installed sticker set, but offers no explicit guidance on when to use versus alternatives, nor any prerequisites such as already having the sticker set installed. The contrast with 'install_sticker_set' is only contextual, not stated.

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