discord_admin_stickers

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

Annotations already mark the tool as destructive and not read-only, so the description adds little beyond that. It does not disclose side effects like permanence of deletion, permission requirements, or response conventions. The phrase 'using JSON-capable endpoints' is vague and provides no concrete behavioral context.

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 sentence that front-loads the core operations. Every word contributes to purpose definition, with no filler or redundancy.

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?

With no output schema and multiple operations, the description should explain return values, error behavior, or pagination for list, but it does none of this. The minimal text leaves the agent under-informed for a multi-operation admin tool with destructive actions.

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 coverage is only 50%, and the description does not clarify the missing itemId parameter or the expected shape of the data body. It merely repeats the operation names found in the schema enum, offering no additional meaning for parameter usage.

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 tool manages server stickers with specific verbs (list, get, create, update, delete). It is immediately distinguishable from sibling tools like discord_admin_emojis or discord_admin_roles, 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?

The description implies use for sticker management through its resource focus and operation list. However, it does not explicitly state when to prefer this over alternatives such as discord_admin_request, nor does it mention any exclusions or prerequisites.

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