get_diary

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

No annotations provided, so description carries full burden. It describes the diary layer, entry frequency, and return behavior. Lacks explicit statement about non-destructiveness, but context implies read-only. Minor gap for full transparency.

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?

Highly concise: one sentence states purpose, paragraph explains distinct layer, then Args section. No fluff, front-loaded with key info.

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 two parameters and existence of output schema, description fully covers tool's behavior, usage, and parameters. Sibling tools are distinct, so no missing context.

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 0%, but description adds full meaning: date values ('latest' or YYYY-MM-DD), n meaning (number of recent entries when date='latest', default 1, max 14). Complements schema.

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 it reads the agent's daily first-person diary, distinguishing it from conversation tools by noting the diary is a separate layer not surfaced by search_personal_memory.

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?

Explicitly explains when to use (to read the diary itself) and when not (since search_personal_memory does not surface it). Arg section details parameter usage: date as 'latest' or specific day, n for count with max 14.

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