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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds a genuinely useful behavioral fact beyond the annotations: 'there is no unlike,' warning the agent that the action is effectively irreversible. It does not explain response behavior, but that is minor for a one-way toggle.

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?

Two tight sentences with no filler; the action and the irreversibility caveat are front-loaded, and the required inputs follow immediately. Every clause earns its place.

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 two-parameter mutation with no output schema and annotations that already convey the safety profile, the description covers the action, the required inputs, and the no-unlike caveat. It could optionally note the resulting feed effect (e.g., like count), but nothing essential to correct invocation is missing.

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% and both parameters are documented in the schema (position_id, owner_username with provenance 'from the feed row'). The description restates the two required inputs and their source but adds no syntax, format, or validation detail beyond the schema, so the baseline of 3 is appropriate.

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 ('Like') and resource ('another member's trade on the live-trades feed'), which cleanly separates it from nearby siblings such as live_trades_feed, follow_trader, and watcher_trades. An agent can identify the action without opening the schema.

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 tells the agent exactly what inputs are needed ('the trade owner's username and the trade's position_id') and implicitly scopes usage to the live-trades feed, plus flags that no inverse operation exists. It stops short of naming an explicit when-not or an alternative tool, so it is clear context rather than full routing guidance.

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