list_recent

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

No annotations provided, so description carries full burden. It discloses ordering (most recent first), default limit (50), max limit (1000), filter behavior (day sets since/until), and pagination via offset. No destructive behavior mentioned, which is appropriate for a read-only listing tool.

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?

The description is densely packed with useful information and is front-loaded with the core purpose. While it spans multiple sentences, each adds value. A minor reduction for not being more terse, but it's still efficient for the complexity.

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?

The tool has no output schema, so description should hint at return format. It doesn't mention that responses include link details, but given the tool name and sibling context, it's fairly complete in explaining filtering and pagination. A more explicit mention of the response structure would push this to 5.

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%, but description adds significant value: for `limit` it says 'increase before assuming a link isn't there', for `day` it says 'sets since/until automatically', for `offset` it explains pagination use. The text contextualizes each parameter beyond 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?

Clearly states it lists recently opened links, ordered by most recent first. This distinguishes it from sibling tools like `list_links` (likely all links) and `search` (query-based). The verb 'list' and resource 'recently opened links' are specific.

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?

Provides explicit guidance: if initial results not found, increase `limit`, use `offset`, or filter by `day`/`since`/`until`. Recommends `day` over scrolling and advises against giving up early. This is exemplary usage direction.

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