like_post

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

No annotations are provided, so the description carries the full burden of disclosing behavior. "Like a LinkedIn post" only states the action without mentioning authentication requirements, potential side effects, or any return value. This is a significant transparency 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?

The description is extremely concise, with a single sentence and no unnecessary words. However, it is under-specified, lacking contextual details that would enhance usefulness. It earns points for brevity but loses for not providing enough substance.

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 tool is simple, but the description does not address prerequisites like authentication or existing session requirements. There is no output schema and no annotations, leaving the agent without critical context for invoking the tool correctly. The description is too minimal to be complete.

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 both post_url and profile_id having descriptive text in the input schema. The description itself adds no further parameter meaning, but since the schema fully covers the parameters, the baseline score of 3 applies.

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 "Like a LinkedIn post," which clearly identifies the action (like) and the resource (LinkedIn post). It distinguishes itself from sibling tools like comment_post and like_and_comment_post by specifying the exact action being performed.

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?

There is no guidance on when to use this tool versus alternatives. For example, like_and_comment_post combines liking and commenting, and the description gives no indication of when to choose one over the other. It also fails to mention prerequisites such as being logged in or having an active session.

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