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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the returned field set, which is useful context, but says nothing about pagination, result limits, ordering, or whether archived programs are included by default.

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 compact line with the resource front-loaded and no wasted wording. It is a noun phrase rather than a sentence, so it reads as a field inventory instead of a purpose statement, but nothing is redundant.

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 one optional parameter, no output schema, and full annotation coverage, the tool is simple, and listing the returned fields partially compensates for the missing output schema. Still, there is no statement of result volume, ordering, or default filtering, which an agent needs to use the results correctly.

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% and the single 'status' parameter is fully documented with an enum in the schema, so the baseline is 3. The description mentions 'status' only as a returned field, which slightly blurs whether it is a filter, but adds no real semantics beyond the 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?

The description names the resource ('Stamp-card programs') and enumerates the fields it returns, which lets an agent infer a read/list operation. However, it never states a verb such as 'list all' and does not differentiate it from siblings like list_near_reward or get_analytics, so the purpose is implied rather than stated.

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?

There is no when-to-use guidance, no mention of the optional status filter as a selection mechanism, and no routing to alternatives such as update_program or archive_program. The agent must guess that this is the enumeration tool for programs.

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