Save Post

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

The description discloses an important behavioral trait: the legacy save endpoint is best-effort and cannot always confirm synchronously, so the result must be verified in the Saved collection. This goes well beyond the idempotentHint annotation and helps set expectations for the agent.

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 short sentences, front-loaded with the core purpose and followed by a concise caveat about synchronous confirmation. Every word adds value with no repetition or fluff.

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 complete for a tool with an output schema, idempotentHint annotation, and full schema parameter coverage. It covers the essential context of identity targeting and the best-effort backend behavior, though it stops short of mentioning the unsave_post sibling or the confirm parameter requirement explicitly (both are inferable).

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%, so parameters (post_id, confirm, account_id) are already well-documented in the schema. The description adds no additional parameter-level information, but it does reference the active/specified identity concept that maps naturally to account_id.

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: 'Save/bookmark a post to the active (or specified) identity's Saved.' This clearly identifies the tool's action and target, and it is implicitly distinguished from the sibling unsave_post.

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?

Provides clear context by indicating the action applies to the active identity or a specified identity via account_id. It does not explicitly mention alternatives like unsave_post or when not to use, but the purpose is unambiguous and the identity-scoping guidance is useful.

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