Create sticker

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

Annotations provide only readOnlyHint=false and destructiveHint=false, so the description adds valuable context by specifying file type requirements (png, apng, gif), dimensions (320x320), size limit (512 KB), and server slot constraints. This goes beyond the structured data, though it does not mention error behavior or permission requirements.

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?

Two concise sentences convey the core purpose and key constraints without fluff. The information is front-loaded and every clause adds value.

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 has 5 parameters and no output schema, and the description covers the creation purpose and critical constraints. However, it omits return value expectations, permission prerequisites, and failure modes, which are relevant for a create operation. Still, it is adequate for basic invocation.

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 input schema already describes tags, guild, and description (60% coverage). The description adds meaning for image_url by stating it is the image source and giving format constraints, but it does not clarify the 'name' parameter beyond the general creation context. Overall, the description supplements but does not fully compensate for undocumented parameters.

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 opens with a specific verb+resource: 'Upload a custom sticker from an image URL.' It clearly identifies the tool's function and differentiates it from sibling tools like update_sticker and delete_sticker by focusing on creation.

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 when to use this tool (to create a sticker) and adds context about format and slot limits, but it does not explicitly mention alternatives like update_sticker for modifying existing stickers or list_stickers for viewing. No when-not-to-use guidance is provided.

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