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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so "no points are changed" largely restates structured data. The description does add useful context — that this is an audit-oriented ledger view and that it targets the V3 / Loyalty 2.0 API — but says nothing about volume, rate limits, or result ordering.

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?

Front-loaded with the report's identity and contents, then the read-only caveat, then the API path. The parenthetical field list is dense but each item is informative; only the trailing endpoint string is arguably filler.

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 usefully enumerates the payload contents (rule, points, event, order id/breakdown, customer id), which is exactly what an agent needs to decide whether to call it. Pagination is covered by the schema, so its absence from the description is not a real gap.

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 description coverage is 100%: both `page` and `limit` are documented in the schema, including the more_pages/next_page guidance and the 1-100 range. The description adds no parameter detail, so baseline 3 applies.

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 (list/report) and resource (loyalty activities = points ledger) and enumerates the fields returned (rule, points credited/debited, event, order id, customer id). It is clearly distinct from stamped_get_customer or stamped_list_orders, though it never explicitly contrasts itself with the closest sibling, stamped_list_loyalty_rewards.

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?

"Read-only audit view" implies the use case (auditing the points ledger), but there is no explicit when-to-use/when-not or routing to alternatives such as stamped_list_loyalty_rewards for the reward catalog. Usage must be inferred from the field list.

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