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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond them—the account-connection prerequisite and the fact that active status is included in the result. It says nothing about ordering, pagination, or what happens with zero alerts, but for a parameterless read that is a modest gap.

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 the resource, the returned field, and the prerequisite all front-loaded. Nothing is redundant or padded.

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 zero-parameter read with no output schema, the description conveys the shape of the result (alerts plus active flag) and the auth precondition. Only minor details like empty-result behavior are absent, which is acceptable at this complexity.

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 no parameters, so the description carries no parameter burden and the baseline of 4 applies. It correctly restricts scope to the connected user's own account rather than any parameterized filter.

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 alerts saved on the user's Buzzedin account') and adds the returned attribute ('whether each is active'). It doesn't explicitly distinguish itself from siblings like save_alert or get_my_matches, but the read-only 'list my alerts' framing is clear enough to separate it from the mutation siblings.

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 a prerequisite ('Needs the user to connect their Buzzedin account'), which tells the agent when the call will fail. It offers no guidance on when to prefer this over save_alert or get_my_matches, so usage is only implied by the verb.

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