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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the auth prerequisite and the content of what is returned. It does not cover ordering, pagination, or behavior on an empty list, which is the remaining gap for a list tool with no output schema.

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: what is listed, what each entry contains, when to use it, and the auth requirement. No redundant restatement of the title or annotations, and every clause carries distinct information.

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?

With no output schema, the description carries the return-shape burden and does so at a summary level (event email arrival times, followed teams) plus the sign-in requirement. Ordering, volume, and pagination behavior remain unstated, which is a minor gap for a zero-argument list tool.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. The description correctly implies no filtering or scoping arguments exist.

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 and resource ('List the reminders on the signed-in user's beep.me account') and enumerates the two record kinds returned (upcoming events with email arrival times, followed teams). That enumeration clearly separates it from siblings like search_events or remind_me.

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?

Gives an explicit trigger ('when the user asks what beep.me reminds them about') and an explicit downstream use ('before stop_reminder to find the id'), naming the sibling that depends on it. It also states the precondition (user signed in), so no inference is required.

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