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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered. The description contributes the ordering guarantee and the availability of pagination/date filtering, but says nothing about return shape, page-size caps, or how the two keyset cursors must be paired.

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?

Two tight sentences with the core behavior front-loaded and no filler. The second sentence is somewhat generic boilerplate ('supports pagination and date filtering') but earns its place by flagging cap ability the agent might otherwise miss.

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 read-only list tool with no output schema, the description names the ordering, the filtering dimension and the pagination capability, which matches the schema's surface area. It does not explain the keyset cursor pairing (before_id + before_opened_at) or what fields come back, but annotations carry the safety profile.

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% across all 7 parameters, so the schema already explains sort, limit, query, since/date_to and the two cursors. The description's 'pagination and date filtering' phrasing adds thematic grouping but no syntax or pairing rules 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?

States a specific verb+resource ('Get recently read articles') plus the ordering rule ('ordered by when they were opened'), which cleanly separates it from read-later siblings like get_saved and get_articles. It never names a sibling explicitly, so it stops short of full differentiation.

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 'recently read' scope implies when an agent would reach for this over get_articles or get_saved, but there is no explicit when-to-use statement and no named alternative. Usage is inferable rather than stated.

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