Unsave Post

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

The description adds significant behavioral nuance beyond the annotations: it describes the operation as 'best-effort' with the legacy endpoint, notes that confirmation may not be synchronous, and instructs verifying in the Saved collection. This transparency about asynchronous behavior and follow-up action is highly valuable.

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 two sentences: the first clearly states the purpose, the second explains a key behavioral caveat. There is no fluff or repetition, and the most important information is front-loaded.

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 description is sufficient for this simple tool: it covers the main action and a critical behavioral caveat. The confirm parameter's requirement is already in the schema, and an output schema exists, so return values need not be described. The lack of an explicit mention of confirm=true is not a gap since schema covers it.

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%, with each parameter (post_id, confirm, account_id) already described in the schema. The description's phrase 'active (or specified) identity' restates the account_id default but adds no new meaning beyond 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 'Remove a post from the active (or specified) identity's Saved' with a specific verb (remove), resource (post from Saved), and scope (identity). It clearly distinguishes this from sibling tools like save_post (adds to Saved) and delete_post (removes the post entirely).

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?

Usage is implied by the purpose (use when you need to unsave a post), but there is no explicit guidance about when to use versus alternatives or any exclusions. The description does not mention that save_post is the complement, nor does it explain that delete_post would permanently delete the post rather than just removing it from Saved.

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