skylight_unlike_message

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

Without annotations, the description carries the behavioral burden; it discloses the core effect of removing a like but not edge behavior such as whether removing a non-existent like is an error, whether it affects only the current user, or what the response is.

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?

Eight words with no filler; the verb and object are front-loaded and every word contributes to the meaning.

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?

For a low-complexity mutation with two parameters and no output schema, the description covers the core call intent but remains thin: no parameter semantics, no return/error behavior, and no guidance around the like_message counterpart. It is minimally viable with clear gaps.

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 0% and the description only hints that id identifies a message/photo. It does not explain the relationship between id and frameId, nor why frameId is optional, so the description only partially compensates for the undocumented schema.

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 states a specific action and resource: 'Remove a like from a message/photo.' It is clear and naturally contrasts with the sibling skylight_like_message, but it never explicitly names that alternative.

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 action verb 'remove' implies this tool is used to undo a like on a message/photo, so usage is inferable. However, there is no explicit statement of when to choose this over skylight_like_message or any preconditions such as an existing like.

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