List Discord stickers

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond the guild scoping already implied by the tool name — no pagination behavior, no statement of whether only guild-specific stickers (not built-in ones) are returned.

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 short sentence with no padding, front-loaded on the verb. It is arguably under-specified rather than verbose, but as raw conciseness it is efficient.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a list operation the description omits pagination/limit behavior and the scope of stickers returned, leaving a real gap before an agent can call it confidently.

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?

There is one parameter, guildId, with 0% schema description coverage — only a regex pattern constrains it. The description's phrase 'in a Discord guild' only weakly signals that guildId is required and does not explain the 17-20 digit snowflake format or where to obtain it.

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?

States a specific verb ('List') and resource ('stickers') scoped to a Discord guild, so the operation is unambiguous. It doesn't distinguish itself from sibling list tools like discord_list_emojis, which is the nearest same-kind resource, but the resource name alone is fairly distinctive.

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?

No guidance on when to use this versus alternatives such as discord_list_emojis, nor any stated prerequisites (e.g., needing a guild ID resolved via discord_list_guilds). The agent must infer usage entirely from the name.

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