RecallNest

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

No annotations provided, so description carries full burden. It explicitly states 'Read-only' (critical safety info) and describes sorting behavior ('sorted by creation date') and return structure (four specific fields). Deduct one point for missing error handling or empty-state behavior.

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 total. First sentence front-loads action, resource, and key behavioral traits. Second sentence provides usage context. Zero redundancy—every word 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?

No output schema exists, but description compensates by enumerating the four fields returned. With single parameter and no annotations, description adequately covers tool behavior. Minor gap regarding null/empty result handling.

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 has 100% description coverage for the 'limit' parameter including default/max values. Description does not explicitly discuss the parameter, but with complete schema coverage, baseline 3 is appropriate as the schema carries the semantic load.

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?

Description explicitly states 'List pinned memory assets' with specific verb and resource. It distinguishes from siblings by referencing 'explicitly pinned via pin_memory' and specifies output fields (title, scope, importance score, file path), clearly defining scope.

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 when-to-use guidance: 'review high-value memories that were explicitly pinned via pin_memory' and 'check if a topic already has a pinned reference before creating a new one.' Names sibling tool pin_memory directly as the complementary operation.

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