RecallNest

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

With no annotations provided, the description carries the full burden. It adds valuable behavioral context with 'durable memory' and 'across fresh windows,' indicating persistence across sessions. However, it omits critical behavioral details like update/merge semantics (only hinted at in the schema's canonicalKey description), failure modes, or durability guarantees.

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 consists of exactly two high-value sentences: the first defines the action and target, the second provides usage context with examples. There is no redundancy or extraneous text; every word earns its place with purpose-driven, front-loaded structure.

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 complexity (10 parameters, structured workflow concept) and absence of annotations or output schema, the description provides adequate but minimal coverage. It successfully conveys the core concept and usage trigger, but could enhance completeness by explaining the workflow lifecycle, canonicalKey behavior, or how stored patterns relate to retrieval mechanisms (retrieve_skill is a sibling).

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, the baseline is appropriately 3. The description implies the conceptual structure (title, trigger, steps) through the 'workflow pattern' concept and examples, but does not add specific parameter semantics, syntax guidance, or clarify the scope format beyond what the schema already documents.

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 'Store a reusable workflow pattern as durable memory' with a specific verb (store) and resource (workflow pattern). It effectively distinguishes from siblings like store_memory, store_skill, and store_case by specifying 'workflow pattern' and providing concrete examples (startup continuity, debugging routines) that imply structured, step-based processes rather than facts or capabilities.

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 provides clear positive guidance: 'Use this when you identify a repeatable process worth reusing across fresh windows' followed by specific examples. However, it lacks explicit negative constraints (when not to use) or named alternatives, though the examples implicitly differentiate it from other storage tools.

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