List installed sticker sets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, which cover the safety profile. The description adds minimal behavioral context, simply stating the return value. It does not disclose pagination, authentication, or the role of the optional accountId.

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 a single concise sentence that front-loads the verb 'Return' and states the resource. No extra words, perfectly scoped.

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?

The tool is a simple getter with a read-only annotation, so the description is mostly adequate. However, without an output schema, the return format is unclear, and the optional accountId is not explained. The description is minimal but sufficient for the core function.

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 contains one parameter (accountId) with no description, and the description does not mention it. Schema description coverage is 0%, so the description fails to explain how accountId affects the call or whether it defaults to the current user.

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 uses a specific verb ('Return') with a clear resource ('the user's installed sticker sets'), which distinguishes it from sibling tools like install_sticker_set and add_recent_sticker. It matches the title and leaves no ambiguity about the operation.

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 provides no when/when-not guidance or alternative tool references. It is clear that this is a read operation for listing sticker sets, but there is no explicit comparison to install_sticker_set or add_recent_sticker.

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