collection_set_emoji

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does disclose a key nuance: passing an empty string clears the emoji rather than setting it. However, it does not mention permissions, overwrite behavior, or any side effects beyond the mutation, leaving some uncertainty for a tool with no annotation safety profile.

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 minimal and well structured: one purpose sentence followed by two arg lines. There is no filler, and the important clearing behavior is included efficiently without bloating the 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?

The tool is simple and an output schema exists, so return values need not be described. But the description lacks when-to-use routing relative to collection_edit, error/precondition notes, and any behavioral context beyond the bare mutation. It is adequate for invocation but has gaps an agent might stumble on.

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 schema provides no property descriptions, so the description must compensate. It does so for both parameters: collection_id is explained as the UUID of the collection, and emoji is described with the special empty-string clearing behavior. This is sufficient for a simple two-parameter tool, though it omits format constraints like maximum emoji length or valid emoji characters.

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 and resource: 'Set or clear the emoji marker on a collection.' This is clear and unambiguous. However, it does not explicitly differentiate itself from sibling collection_edit, which could also modify collection fields, so it stops short of full sibling differentiation.

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 gives no guidance on when to choose this tool over collection_edit or other collection tools. It states what the tool does but not the conditions, exclusions, or alternatives that should drive selection. No sibling is named or recommended.

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