Create sticker

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

Despite minimal annotations, the description adds value by disclosing constraints on image format, size, and file size, as well as slot consumption. It does not contradict annotations (readOnlyHint=false) and appropriately indicates a write operation.

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 brief and front-loaded: the first sentence states the purpose, the second provides key constraints. No unnecessary words.

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 creation tool with no output schema, the description covers essential constraints (format, size, file size, slot limits). It does not describe the return value, but the agent can infer success from standard API responses.

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?

With 60% schema description coverage, the description adds minimal parameter-specific information beyond the schema. It explains the image_url content format but does not elaborate on guild, name, description, or tags beyond what the schema already provides.

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 ('Upload a custom sticker') and the resource ('sticker'), distinguishes it from sibling tools like delete_sticker and update_sticker, and specifies the input method ('from an image URL').

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 specific format and size requirements (png, apng, or gif at 320x320 pixels, up to 512 KB) and mentions slot limits ('start with five sticker slots; boosts add more'), giving practical usage context. However, it does not explicitly state when to avoid using the tool or list alternatives.

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