wechat_add_sticker

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

No annotations are present, so the description must disclose all behavioral traits. It only says 'Add a sticker' without explaining side effects (e.g., overwriting, duplicates), authentication needs, or return value details beyond 'Status message'.

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 front-loaded with the one-sentence purpose and uses a clean Args/Returns format. It is reasonably concise, though the section detailing each parameter could be integrated into the main description.

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?

Given the tool has 5 parameters (3 required) and no annotations, the description provides basic parameter context but lacks details on output schema (only 'Status message') and fails to address typical edge cases or integration with sibling tools.

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 description adds meaningful context to each parameter: 'name' is used in placeholders, 'md5' is a hash, 'tags' are comma-separated. This goes beyond the schema's type and title, though it could be more precise about 'file_path' and 'description'.

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 'Add a sticker to the library' with a specific verb and resource, and it distinguishes from sibling tools like 'wechat_list_stickers' and 'wechat_search_stickers' by focusing on addition.

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 is provided on when to use this tool versus alternatives, nor are any prerequisites or conditions (e.g., file existence, permissions) mentioned.

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