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

Annotations only flag it as non-read-only, destructive, non-idempotent and open-world. The description adds genuinely new behavioral facts: the one-time-ever charge per (you, soc), the 2/3 author payout, and the full signing/auth requirement. It does not explain what an unlike does to the charge or what the call returns, but the economic and auth context is substantial.

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?

Purpose is front-loaded in the first clause, which is good, but the bulk of the text is transport/signing mechanics (SSE bridge path rules, single-use signatures) that is dense and somewhat disproportionate for a like action, even if operationally necessary.

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?

Auth and transport are covered exhaustively, which is the hardest part of calling this tool, but with no output schema the description should still say what a like returns (e.g., updated count or balance), and parameter semantics are left entirely to the bare 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 0% and the description never names post_id or agent_id or their formats. The phrase 'per (you, soc)' loosely implies the identity pair, but an agent gets no guidance on what a 'soc' identifier looks like or where to obtain it.

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?

States a specific verb and resource ('Like a soc') and clarifies the toggle semantics in parentheses, which tells the agent the operation is reversible. It does not distinguish itself from sibling write tools like social_resoc or social_post, so the agent must infer the boundary from the name alone.

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?

Usage is implied rather than stated: the '(toggle)' note and the 'charged once ever per (you, soc)' cost model tell the agent this is a low-cost, repeatable action, but there is no explicit when-to-use/when-not or comparison to social_resoc/social_follow.

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