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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: stable tie-breaking by descending ID, pagination continuation semantics, and the caveat that 'Results can change between requests' (non-snapshot reads). It does not cover rate limits or result-size characteristics, keeping it short of a 5.

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?

Mostly dense and front-loaded, but the sentence 'Equal creation times use descending ID order.' is duplicated verbatim, which is wasted text and suggests an editing defect. The rest earns its place, so this is a modest rather than severe deduction.

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?

An output schema exists, so return values need not be explained, and the description still supplies the one output detail an agent must act on: driving the next page from meta.next_offset. For a read-only, filter-and-paginate list tool, nothing needed to call it correctly is missing.

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%, so tags, limit, offset and tag_mode are already fully documented in the schema. The description only restates defaults (limit 50, offset 0, max 100) that the schema already carries, adding no new parameter meaning. 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 and resource ('List Push Notification history for the account') plus ordering ('newest first'), and explicitly distinguishes itself from the sibling get_push_notification for single-notification lookups. An agent can route correctly without opening either schema.

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 use cases (review what was sent, find a public_id, filter by Tags), names the alternative for the single-notification case, and spells out the pagination loop: continue with meta.next_offset using the same filters and stop when it is null.

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