newsletter_unfollow

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

With no annotations, the description carries the behavioral burden. It usefully discloses that confirm=true is required, signaling a deliberate action, but it doesn't describe consequences, reversibility, or what happens when confirm is false or absent.

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 no filler. The key safety constraint ('Requires confirm=true') is front-loaded and clearly separated from the main action.

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, but the description omits what jid represents and any effect of the operation. It is adequate as a minimal callable definition, yet leaves several practical details—such as where jid comes from and outcome of the unfollow—unstated.

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%, so the description must compensate. It adds meaning only for confirm ('requires confirm=true'), while leaving the required jid parameter entirely unexplained in terms of what it identifies and how it should be sourced.

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 'Unfollow a channel' uses a specific verb and resource, clearly distinguishing it from sibling tools like newsletter_follow and newsletter_mute. It directly states the action and target.

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 includes an operational prerequisite ('Requires confirm=true'), but does not explicitly state when to use this tool versus alternatives such as newsletter_mute. Usage context is mostly implied by the tool name and the unfollow action.

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