Лайк публикации

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

Annotations already indicate a write operation (readOnlyHint false). The description adds context that the like is toggled on behalf of the authenticated user and can be both set and removed, but it does not disclose potential side effects or response behavior. No contradiction with the annotations exists.

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 a single, succinct sentence with no filler or redundant context. The core action and the acting identity are front-loaded, making it instantly scannable.

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 only two simple parameters and no output schema, the description plus schema provides enough to invoke the tool correctly. The 'from one's own name' nuance adds useful context, though return-value/error behavior is not described — a minor gap given the low complexity.

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 input schema fully describes both parameters with 100% coverage, so the description does not need to repeat them. The description adds no parameter-specific meaning beyond naming the target publication, keeping it at the baseline for high schema coverage.

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 a specific action (set or remove a like) on a specific resource (a marketplace publication). This clearly distinguishes it from sibling marketplace tools such as market_publish or market_update, which do not involve liking.

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 does not explicitly mention when to use this tool instead of alternatives, nor does it name exclusions. However, the action is self-evident — an agent can infer it should be used when the user wants to like or unlike a publication. The phrase 'от своего имени' offers a light hint that the operation is performed under the user's own identity.

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