List recent SlimSnap captures

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

Beyond the readOnlyHint annotation, the description discloses ordering ('newest first'), preview behavior, and a performance trait ('cheap summary view'). It does not detail the exact content of previews or pagination behavior, but the added context goes beyond annotations.

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, zero waste. The first sentence delivers the core purpose; the second adds context and differentiation. Information is front-loaded and every sentence earns its place.

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 simple list tool with one parameter, an output schema, and a read-only annotation, the description covers the essential behavior, ordering, preview, and usage scenarios. There are no significant 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?

The schema fully documents the only parameter ('limit') with description, default, and range. The description does not need to add parameter semantics; 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?

The description clearly states the action ('Lists'), the resource ('captures'), and the scope ('user's recent'), plus ordering ('newest first') and content ('short text preview'). It also distinguishes itself from the sibling get_capture by framing it as 'the cheap summary view'.

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 clear usage context: 'Useful for finding an earlier capture when the user does not mean the newest one, or for working through several marked screens.' It explicitly names get_capture as an alternative but does not explicitly address get_latest_capture, leaving that distinction implied by context.

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