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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds real context beyond them: results are ordered newest first and each item carries a date, summary and story link, plus a link to the transfer bonus page. It says nothing about volume, caching, or whether older bonuses are archived.

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?

One sentence, front-loaded with the resource, followed by a parenthetical that genuinely earns its place by defining what a transfer bonus is. Dense but not padded; the trailing mention of the transfer bonus page is short and informative.

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 simple read-only, single-optional-parameter list tool with no output schema, the description covers ordering and the shape of returned items well enough to call it correctly. The only omissions are minor: no note on total availability or whether results are capped at 50 beyond the schema's maximum.

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 single limit parameter is fully documented in the schema (max 50, default 10). The description adds only the 'newest first' framing, which clarifies which stories the limit trims, but gives no further semantics. Baseline 3 applies when the schema does the heavy lifting.

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 resource (transfer bonuses reported by the Frog sites) and what constitutes one (extra miles/points when moving bank points like Amex MR or Chase UR to an airline or hotel program). That detail distinguishes it from generic siblings such as list_news or list_articles without needing to name them. It stops short of an explicit sibling comparison.

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?

The description never says when to call this versus search_programs, list_news, or get_points_program, nor does it mention preconditions. Usage is only inferable from the content itself ('transfer bonuses ... newest first'), which is close to no guidance.

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