Recent clips or transcriptions

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

With no annotations, the description carries the burden and does real work: it declares newest-first default ordering, the sort options per entity type, and keyset pagination via meta.next_cursor. It stops short of stating read-only safety, result caps, or what a cursor mismatch does, which the schema only partly covers.

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 sentences, front-loaded with the verb and ordering, followed by quotable intent examples and a compact enumeration of supported features. No filler and no redundancy.

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 an 18-parameter list tool with no output schema and no annotations, the description covers purpose, filters, sorting and pagination, and helpfully names meta.next_cursor. It omits the deleted-flag-to-eve_restore linkage and clipping defaults, but the schema fills those gaps.

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 five of the parameters are enums, so the schema already documents every parameter. The description only restates the sort mode mapping and the meta.next_cursor format, adding little beyond the structured fields; baseline 3 is appropriate.

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 the most recent clips or transcriptions") with an explicit ordering scope ("newest first"), which is enough to distinguish a recency browse from a query search. It never names the sibling eve_search, so the differentiation from search 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?

Concrete user-intent examples ("what did I copy/dictate recently", "recent links from Safari", "my longest dictations") show exactly when to reach for this tool. It does not state when to use eve_search instead, so the when-not/alternative half of the guidance is absent.

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