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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent behavior, so the safety profile is covered. The description adds only a faint scope claim ('retaining the intended text and print-area scope') and says nothing about what session content gets overwritten, that rendering may fetch external image URLs, or that a session token is required — details that live in the schema, not here.

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?

It is a single sentence with no filler, which is good, but the opening is loaded with internal jargon rather than a concrete statement of what happens to the emoji characters. Efficient in length, weak in information density.

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?

This is a destructive mutation with a large nested options object (area scoping, element targeting, replacement arrays, platform selection) and no output schema. One sentence of jargon-heavy prose is not enough to tell an agent how the nested targeting fields interact or what the tool leaves untouched.

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 description coverage is 100%, including per-property descriptions for subject, requestId, and sessionToken, so the schema carries parameter meaning on its own. The description mentions no parameters and adds nothing about the nested options object, so the baseline 3 applies.

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 pairs the verb 'Replace' with the resource 'emoji text' and gestures at the outcome (approved emoji image workflow retaining text and print-area scope). However, it is phrased in internal jargon ('streetshirts' existing approved emoji image workflow') and never clarifies how this differs from siblings like replace_image, update_text, or add_text, so an agent must infer the boundary.

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?

There is no statement of when to choose this tool over replace_image or update_text, no prerequisites beyond what the schema enforces, and no exclusions. The only implicit guidance is 'retaining the intended text and print-area scope', which is a constraint rather than a routing rule.

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