list_recents

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

With no annotations, the description must fully disclose behavior. It only says 'list recent items', implying a read operation, but fails to define what 'recent' means, sorting, pagination, output format, or any limitations. Essential behavioral details are missing.

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?

A single sentence that is front-loaded with the verb and resource, and includes the key modifier ('optional context filter'). Every word serves a purpose; no redundancy. Ideal conciseness.

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 one parameter and no output schema, but the description does not explain what constitutes 'recent items' (e.g., time frame, item types) or the return format. It is adequate for a simple list operation but lacks completeness for efficient selection and use.

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 description adds minimal value over the schema, which already describes the 'context' parameter as 'Context filter (e.g., "views")'. The description simply restates the existence of an optional filter. Baseline 3 is appropriate for high schema coverage, but no additional clarification.

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 ('List'), the resource ('recent items'), and the scope ('in Metabase'). It distinguishes from siblings like list_recent_views (specific views) and list_popular_items (popularity basis). The mention of optional context filter adds precision.

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?

No guidance is provided on when to use this tool versus alternatives like list_recent_views or search. There are no explicit use cases, conditions, or exclusions. The description only states what it does, not when it should be chosen.

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