ListRecentHighlights

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

With annotations already covering read-only, idempotent and non-destructive behavior, the description adds genuinely new operational context: the request budget ('one request for recently updated items and one per item checked (at most 21 requests)') and a correctness caveat that reading progress and tag changes also count as updates, so some highlighted items may go unchecked when more_items is set.

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?

Four sentences, front-loaded with the purpose and use case, followed by the cost model and caveat. Every sentence carries information an agent needs; none is 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?

An output schema exists, so return values need no explanation. For a read-only list tool the description supplies purpose, trigger, request cost and a partial-results caveat, leaving no material gap for correct invocation.

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 both parameters are fully documented there, including the 7-day default for 'since' and the 1-20 range for max_items. The description reinforces the cost of max_items ('one per item checked') but adds no syntax or format detail beyond the schema, 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, resource and temporal scope: 'List the highlights the user made recently, grouped by item.' The 'recently'/'grouped by item' qualifiers implicitly separate it from the sibling Matter_ListHighlights, but no sibling is named explicitly.

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 a concrete usage trigger — 'Use this to answer "what did I highlight this week?"' — which is more than implied context. It does not, however, state when NOT to use it or name ListHighlights as the alternative for full-history queries.

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