get_day

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

No annotations provided; description carries burden. It discloses that tool returns full diary entry with media, implying read-only behavior. However, it does not mention permissions, side effects, or return format beyond a vague 'full diary entry'.

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?

Single sentence of 15 words, front-loading core purpose with no filler. Every word 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?

Given no output schema, description covers what the return includes (text entry plus photos/voice notes). For a single-day retrieval tool, this is sufficient, though more detail on structure would help.

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 description coverage is 100% for the single parameter (date), providing valid values. Description adds no extra meaning to the parameter beyond referencing 'one day's full entry'.

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 clearly states verb 'read back' and resource 'one day's full diary entry', including photos and voice notes. Distinguishes from sibling tools like get_range (multiple days) and add_entry (writing).

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?

Description implies single-day use but does not explicitly state when to use this tool versus alternatives (e.g., get_range for multiple days, on_this_day for historical dates). No when-not-to-use guidance.

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