nexo_diary_archive_search

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

Discloses that diaries older than 180 days are moved here forever, a key behavioral trait. No annotations provided, so description carries burden; it adequately conveys it is a search operation without destructive side effects.

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, front-loaded with purpose and usage examples. No redundant information. Every sentence adds value.

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, so description could detail return format. It omits what the search returns (e.g., list of entries). While functional, it leaves a small gap for agent understanding.

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?

All parameters are described in schema (100% coverage). Description adds no new param details but provides context about archive nature. Baseline 3 is appropriate as schema already covers semantics.

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 tool searches the permanent diary archive for historical lookups, with examples ('last year', 'months ago'). It distinguishes from related tools like session diary tools by specifying it's for older entries moved to archive.

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 examples of when to use ('historical lookups'), but does not explicitly state when not to use or alternatives. The context implies it is for old entries, but could be more explicit.

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