RecallNest

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

Since no annotations exist, the description carries the full burden. It successfully discloses 'Read-only' status and output format ('one-line descriptions'), but omits details about default tier behavior, pagination, or empty result handling.

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 waste. First sentence delivers purpose and safety (read-only). Second sentence delivers usage guidance. Perfectly front-loaded and appropriately sized for a single-parameter discovery tool.

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 the tool's simplicity (1 optional parameter, no output schema), the description adequately covers intent, behavior, and usage. It hints at return format ('one-line descriptions') despite no output schema. Minor gap: doesn't mention the 'advanced' default tier behavior explicitly.

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?

With 100% schema description coverage for the 'tier' parameter, the baseline is 3. The description mentions 'filtered by tier' but adds no semantic details beyond the schema's existing documentation of the enum values and default behavior.

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 explicitly states the action ('List'), resource ('RecallNest tools'), and key characteristic ('filtered by tier'). It distinguishes itself from sibling memory management tools by positioning itself as a discovery/directory tool rather than an operational tool.

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 usage context ('Use when you need to discover advanced or governance tools beyond the core set'), helping agents understand when to invoke this over operational siblings like 'store_memory' or 'search_memory'. Lacks explicit 'when not to use' guidance or named alternatives.

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