Remove a like

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

Beyond the annotations (idempotentHint, destructiveHint), the description reveals a non-obvious behavioral detail: the tool discovers the like record from the post's viewer state rather than requiring a like ID. This helps the agent understand why the like parameter is unnecessary and that it operates on the caller's own like.

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?

Two sentences with no fluff. The action verb is front-loaded, and the second sentence delivers valuable implementation context that justifies why fewer parameters are needed. Both sentences earn their place.

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 simple idempotent mutation with no output schema, the description fully explains the operation and input requirements. The account parameter is documented in the schema, and the return behavior is not critical for correct invocation. A minor gap is the lack of explicit mention of what happens when no like exists, but the idempotent annotation covers this.

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 covers 100% of the parameters with clear descriptions, so the baseline is 3. The description adds a small reinforcement that only the post is needed, but this does not meaningfully extend the parameter documentation already present in the 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 verb ('Remove') and resource ('your like from a post'), clearly identifying the tool's action. The added detail about finding the like record from the post's viewer state distinguishes it from like_post and other sibling actions, leaving no ambiguity about scope.

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 clearly conveys when to use this tool—when removing your own like from a post—and explains that only the post URI is needed. It does not explicitly name alternatives or exclusions, but the action is so straightforward that the context is sufficient for correct selection.

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