Read posts you have liked

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

Beyond the readOnlyHint annotation, the description adds ordering ('newest first') and a critical scoping constraint (only works for your own accounts). These disclose behavior not covered by structured annotations.

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 front-loaded sentences, first stating the primary function and second adding a necessary constraint. No fluff; 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?

Given the tool has no output schema, the description sufficiently conveys what the operation returns (list of liked posts, newest first). However, it omits pagination details (cursor mechanism) which an agent might need, but that is partially covered by the parameter schema.

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 67%, with limit and account documented. The description mentions 'connected account' which reinforces the account parameter, but it does not add details about cursor pagination or error handling. The description adds minimal semantic value 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 clearly states the tool returns posts a connected account has liked, newest first. The verb 'read' and resource 'posts you have liked' differentiate it from sibling tools like get_post_likes (which likely list likers of a specific 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?

The description gives explicit conditions: 'Only works for your own accounts' and explains why ('because Bluesky does not expose anyone else's likes as a feed'). It does not explicitly mention alternatives, but the restriction guides when to use this tool over others.

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