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

The word 'reversible' is the only behavioral disclosure and does add some value by hinting that the like can be undone or toggled. However, with no annotations provided, the description carries the full burden and fails to clarify whether calling it again unlikes the listing, what side effects occur, or what authentication/error behavior applies.

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?

Being short is not the same as being well-structured. Two words convey too little information to be considered appropriately concise; the description is under-specified rather than efficiently complete.

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 tool with no annotations, no output schema, and an undocumented required parameter, 'Reversible like' is drastically incomplete. An agent cannot determine the exact effect, the expected response, or the meaning of guest_token, making correct invocation uncertain.

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 coverage is only 50%: the 'id' parameter is documented but 'guest_token' has no schema description. The description adds no parameter-level meaning and does nothing to compensate for the undocumented guest_token, so an agent must guess what that token is or where it comes from.

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 phrase 'Reversible like' is a fragment that closely restates the tool name rather than stating the operation explicitly. It implies liking a listing, but it never says 'like or unlike a listing' or names the resource, leaving the exact purpose to inference.

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 no guidance on when to use this tool versus any sibling tool, nor does it mention prerequisites, alternatives, or conditions. An agent has no contextual basis for choosing like_listing over list_listings, get_listing, or create_listing.

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