copy_day

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

Discloses additive, non-destructive nature. Annotations are consistent and description adds context beyond them. Could mention what happens if no entries exist or return format.

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?

Extremely concise: three sentences total, front-loaded with the key behavior, no wasted words.

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?

Covers core behavior well for a simple tool with one optional parameter and an output schema. Lacks mention of error conditions or return value specifics.

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?

Explicitly describes the date parameter format (YYYY-MM-DD) and default value (today), adding semantic meaning beyond the schema's type-only definition.

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?

Clearly states the action (copy), source (previous day), and destination (given date). Distinguishes from sibling tools like add_food_entry or mark_day_complete.

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?

Implies when to use (copying previous day's entries), but lacks explicit guidance on alternatives or when not to use. Does not mention moving vs copying or other scenarios.

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