Like a post

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action and input sourcing; it does not mention side effects, authentication requirements, error behavior, or return values. This is a significant gap for a mutation tool.

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?

Despite limited detail, the description is efficient and front-loaded. The action is stated first, and the parameter source guidance is given in a single extra sentence. No wasted words.

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 like action, the description provides the essential 'what' and 'how to get inputs,' but omits expected return value, idempotency behavior, and potential failures. With no annotations or output schema, more context would be valuable to fully inform the agent.

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 has 0% coverage, but the description compensates by telling users exactly where to obtain the uri and cid (from other named tools). This adds meaningful guidance beyond the bare string types 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 clearly states the action ('Like a post') with a specific verb and resource. It distinguishes from other sibling tools like repost or follow, and even tells where to obtain the needed identifiers.

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 provides clear context by instructing users to get the uri and cid from specific tools (bluesky_get_post, bluesky_get_timeline, bluesky_search_posts). However, it does not explicitly mention when not to use it or name alternatives like bluesky_unlike.

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