Copy Food Entries Between Dates

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

Annotations indicate non-readOnly and non-destructive. The description confirms it is a copy (mutation without destruction) and mentions a return of 'Confirmation'. This adds context beyond annotations, but does not cover all behaviors like error states.

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 at two sentences plus a clean args list. The purpose is front-loaded in the first sentence, and 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?

For a simple copy tool with two parameters and no output schema, the description covers what it does, parameters, and return value. It is fully adequate for an agent to invoke correctly.

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 descriptions are minimal ('Source date', 'Target date'). The description adds format hints ('YYYY-MM-DD'), which improves understanding beyond the schema, even though coverage is 100%.

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 action ('Copy all food entries from one date to another') and the resource ('food entries'). It distinguishes from sibling tools like fatsecret_copy_saved_meal_to_diary by specifying it copies entries between dates, not saved meals.

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 a clear use case ('Useful for repeating a day's meals') that implies when to use. However, it does not explicitly mention when not to use or alternatives, though sibling tools cover other copy operations.

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