Stop following a Hyperliquid address (writes to your account)

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the description does not need to restate that it mutates state. It does add real value beyond them by scoping the destruction: alerts stop but recorded history is preserved, which tells the agent what is and isn't lost. It does not mention behavior for an unknown or stale id.

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 short sentences with the trigger front-loaded and the side-effect clause second. No filler, no restatement of the title.

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 one-parameter mutation with rich annotations and no output schema, the description covers when to call it, where the id comes from, and what happens to existing data. Only the failure mode for an invalid id is unaddressed, which is a minor gap.

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?

There is one required parameter with 100% schema coverage, which already states it is the id from list_tracked_addresses. The description repeats that same fact rather than adding format, validation, or lookup guidance, so it sits at the baseline.

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 action and resource — stop following/tracking a Hyperliquid address — with a clear trigger phrase. It is immediately distinguishable from the opposite sibling add_tracked_address and from the read-only list_tracked_addresses.

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?

"Call this when the user asks to stop following or tracking a Hyperliquid address" gives an explicit trigger, and it directs the agent to obtain the id from list_tracked_addresses. There are no explicit exclusions, but for a single-purpose toggle the invocation context is unambiguous.

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