upload_sticker_pack

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

Discloses that the pack is stored indefinitely on Signal's CDN. No annotations provided, but the description adequately covers the non-destructive nature and outcome. Could mention permissions or overwrite behavior, but not critical.

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?

Five sentences, no fluff. First sentence states main function, then input, output, usage guidance. Well-structured and 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?

Given one parameter and no output schema, the description explains input, output URL, indefinite availability, and correct usage. It doesn't cover error handling or rate limits, but is sufficient for a simple upload tool.

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 single parameter 'path' is described in schema as 'Local path to manifest.json or a zip...' and the description adds context that the manifest describes the pack. Schema coverage 100%, so baseline 3, but the description adds a slight extra nuance.

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 packages and publishes sticker packs to Signal's CDN, specifying input types (manifest.json or zip) and output (a signal.art install URL). It distinguishes from the sibling tool add_sticker_pack, which installs packs.

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?

Explicitly states when to use (create and distribute custom sticker packs) and when not to (use add_sticker_pack for installation), with a clear alternative mentioned.

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