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

Annotations declare destructiveHint=true and idempotentHint=true, and the description adds real value beyond them: the account/API-key requirement, that all notices for the base are removed, and that responses are private/no-store with no email or push. These confirm and enrich the destructive profile rather than contradicting it.

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 purpose is front-loaded correctly, but the remaining bulk is off-topic boilerplate about following in general ('Following grants no private access', 'Up to 50 hosted public bases', 'Updates show the latest published version', 'Repeated publication...'). Only two of these clauses are relevant to unfollowing; the rest is noise that dilutes the actionable content.

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 essentials for calling the tool are present: the effect of unfollowing, the auth prerequisite, and (via annotations) its destructive/idempotent nature, with the only parameter fully specified by the schema. No output schema exists, but the return-value gap is not filled either, and the unrelated follow-documentation leaves the description feeling padded rather than 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 100% and the single base_id parameter is fully documented in the schema (64 lowercase hex chars). The description adds no format or syntax detail beyond that, so baseline 3 applies.

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 opening sentence gives a specific verb+resource+effect: 'Stop following a base and remove its notices.' This clearly distinguishes it from the inverse sibling follow_base, though the description never names that sibling explicitly. Purpose is unambiguous 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?

It states a prerequisite ('Requires a personal account or personal API key'), which is useful, but never says when to choose unfollow_base over related siblings like get_base_following or list_followed_bases, nor any when-not-to-use condition. Usage is only implied.

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