list_flame

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

With no annotations provided, the description carries the burden of disclosure. It discloses key behavioral traits: the 24-hour countdown, the AI triage fields (strategy, relevance, novelty, hook), and time remaining. It doesn't explicitly state read-only, but the action 'list' is inherently non-mutating and the added detail goes beyond the minimum.

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 with zero fluff. The main action and key context are front-loaded, and every part adds meaningful information.

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 description covers what the tool does, what information it shows, and when to use it. It also explains the output contents (triage info and time remaining), which compensates for the lack of an output schema. For a simple list tool with one optional parameter, it is complete.

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%—the only parameter (limit) is fully described in the schema with default value. The description adds no extra parameter detail, so the baseline of 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 uses the specific verb 'List' with a defined resource ('bookmarks in your Flame inbox'), and clearly distinguishes this from siblings like list_vault or list_sparks by highlighting the 24h countdown and AI triage info.

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?

It provides a clear use case: 'Use this to see what needs attention before it burns to Ash.' While it doesn't name alternatives explicitly, the context of the Flame inbox and the urgency implied by the countdown gives strong situational guidance.

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