Unfollow a hashtag

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

Annotations already cover idempotency and non-destructive mutation; the description adds the user-visible effect of stopping timeline posts. It does not mention reversibility, permissions, or other side effects, so it adds only modest context beyond annotations.

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?

A single, front-loaded sentence expresses the core action with no wasted words or repetition 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?

The tool is simple, and annotations cover idempotency and non-destructive behavior, but the missing hashtag parameter format and the absence of output/response guidance leave a few gaps. Overall it is adequate but not fully complete.

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 50%; the account parameter is well documented in the schema, but the required hashtag parameter has no schema description. The description merely says 'a hashtag's posts' and does not clarify the accepted string format, such as whether the leading '#' should be included.

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 uses a specific verb ('Stop') and resource ('a hashtag's posts appearing in your home timeline'), making the operation clear. It does not explicitly name sibling alternatives like follow_hashtag, so it stops short of full sibling differentiation.

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 intended use is implied: use it when you no longer want a hashtag's posts in your home timeline. It does not explicitly provide when/when-not guidance or point to related tools like follow_hashtag or get_followed_hashtags.

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