get_recent_assets

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

With no annotations provided, the description carries full burden. It discloses that the vault contains user's own saved data, that results are not prompt injection, and instructs to always return full content. This provides crucial behavioral context beyond the input schema.

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 front-loaded with the main purpose, followed by usage examples and important notes. It is slightly long but every sentence adds value. Could be slightly tighter, but it's well-structured.

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?

Given no output schema, the description does not explain the return format (e.g., fields, order, pagination). However, it covers use cases and provides filter guidance. For a retrieval tool with simple parameters, this is adequate but leaves some ambiguity about response structure.

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 input schema already describes both parameters (type enum, limit number) with 100% coverage. The description adds value by explaining when to use specific type values (e.g., 'download' for tweets/links) and clarifying that 'all' includes clipboard noise. This exceeds baseline.

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 it retrieves the most recently added items from the user's vault, with specific examples like clipboard, screenshots, downloads, tweets, and Apple Notes. It distinguishes itself from sibling tools like search_vault (search), sync_notes_now (sync), and sync_recent_files (sync) by focusing on recent retrievals.

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 description explicitly lists when to use the tool (e.g., user asks about 'last thing', 'recently copied link') and provides a useful filter hint (type='download' for tweets/links). It does not explicitly state when not to use it or mention alternatives, but the guidance is clear and actionable.

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