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

Annotations already declare destructive=true, idempotent=true, openWorld=false, so the safety profile is covered; the description adds real context on top: an auth requirement ("Needs the user signed in to beep.me") and the differing blast radius of the two modes — one event vs. *every* match of a followed team. Silent on what happens if the ID no longer exists or on partial-failure behavior.

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 sentences, front-loaded with the action and its two modes, then the usage guard and auth precondition. No restatement of the title and no filler.

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 destructive, unauthenticated-by-default mutation with rich annotations and no output schema, the description covers scope, auth, and the stop-only-when-asked rule. The one gap is that required_parameters is 0, yet neither an empty call nor an event_id+follow_id call is addressed, leaving a real invocation ambiguity.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: follow_id cancels all matches of a followed team rather than a single item, and both IDs originate from my_reminders. It does not state whether the two parameters are mutually exclusive or what the precedence is if both are supplied.

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 + resource ("Stop one reminder") plus the two addressing modes (event by event_id, followed team by follow_id), and anchors the IDs to my_reminders, a sibling tool. An agent can distinguish this from remind_me/follow_team without opening a 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?

"Only when the user asked to stop it" is an explicit gating condition that rules out proactive cancellation, and pointing at my_reminders tells the agent where the IDs must come from. It stops short of naming alternatives (e.g., unfollowing vs. stopping) or what to do when the user hasn't specified an ID.

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