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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: a hard cap of 8 results, and the free-plan rule that the newest matches stay hidden until the alert email is sent, which explains apparently missing data. It does not describe ordering beyond 'newest' or how matches are deduplicated, so the added context is useful but partial.

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?

Three short sentences, front-loaded with the core behavior, followed by the result cap, the plan-gating caveat, and the auth prerequisite in order of importance. No redundant restatement of the title or annotations, and every sentence carries information an agent would otherwise have to guess.

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 compensates by stating the result set is capped at 8 and that records carry 'the same details as search_listings,' which lets the agent infer the return shape from a sibling. Combined with the auth requirement and free-plan caveat, an agent has enough to call it and interpret an empty result. Minor gaps remain around ordering and whether matches persist after being shown.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no filtering inputs are needed, matching the empty schema.

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: 'show the newest listings that matched the user's Buzzedin alerts.' It also pins down the scope (up to 8, matching alerts only) and points to search_listings for the detail shape, which separates it from search_listings (all listings) and list_my_alerts (alert configs, not results). It stops short of explicitly naming those siblings as alternatives, so it is clear but not maximally differentiated.

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 concrete usage context: this is the tool for seeing matches from the user's alerts, and it discloses the prerequisite that the Buzzedin account must be connected. The free-plan caveat tells the agent results may appear empty or incomplete in a specific case. There is no explicit 'use X instead when...' routing statement, which keeps it below a 5.

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