Prepare: Copy Food Entries (FatSecret)

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

The description adds the 'dry-run' concept, which helps clarify non-execution behavior. Annotations already indicate not read-only, so there is no contradiction. However, it does not disclose what 'prepare' actually does (e.g., persists a draft operation), any validation steps, or side effects like storing temporary data.

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?

The description is a single sentence, efficiently conveying the core action and modality. No filler or redundant content.

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?

The tool has 4 parameters, no output schema, and is one of many prepare_* tools. The description does not explain the preparation workflow, how the result should be used, or the purpose of 'reason'. An agent would lack crucial context to know what to do after invoking this tool.

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%, so the description has the burden of explaining parameters. It only mentions from/to dates, leaving 'reason' completely unexplained and 'meal' unaddressed. The description adds minimal value beyond the parameter names in the 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 the specific action: 'prepare copying one day's food entries to another date' with the 'dry-run' qualifier. This distinguishes it from sibling tools like create/edit/delete and aligns with the 'prepare' prefix.

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?

The description implies a preparation step before a copy, but explicitly saying 'dry-run' gives some usage context. However, it does not mention that this is a prerequisite for commit_prepared_operation, nor does it distinguish this from other prepare_* tools beyond the copy verb.

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