Like/Unlike Post or Comment

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

The description adds useful context beyond annotations: the action is performed 'acting as the Page,' and the 'unlike' parameter changes the behavior from liking to removing a like. The annotations already indicate mutating, non-destructive, idempotent behavior, so the description supplements rather than repeats them.

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 short and front-loaded with the core purpose, followed by a compact Args list. The object_id line duplicates the schema's description, but the page_id and unlike explanations add value, so the overall structure is efficient.

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 three-parameter tool, the description covers the operation, acting identity, and parameter semantics. It does not describe return values or error conditions, and there is no output schema, but the annotations and provided parameter details are enough for an agent to select and invoke the tool correctly.

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 only 33%, so the description carries most of the parameter-meaning burden. It explains that object_id is a Post or Comment ID, page_id is the Page ID used for the token, and unlike controls whether the like is removed. This meaningfully compensates for the sparse 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 specific verb and resource: it likes or unlikes a page post or comment while acting as the Page. It is immediately distinguishable from all sibling tools, none of which perform this exact like/unlike action.

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 implies when to use the tool: whenever the agent needs to like or unlike a Page post/comment. However, it provides no explicit guidance about alternatives, prerequisites, or when not to use it.

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