Prepare portable memory import

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

Annotations already declare write/non-destructive/non-idempotent, and the description adds genuinely useful behavior beyond them: it is merge-only, it updates the listed entities, omitted entries and safety constraints are left unchanged. It omits confirmation/auth requirements for the staged action, which keeps it from a 5.

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?

A single dense sentence with the core action front-loaded before the contrast clause; no filler. The colon-and-semicolon structure packs a lot in, though the length is near the point where it could be split for clarity.

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 one-parameter tool with no output schema and full annotation coverage, the description covers what changes and what is preserved. The main gap is not explaining the staged prepare→confirm flow or input constraints, but otherwise it is sufficient 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?

One parameter with 0% schema description coverage, so the description carries the burden. It does tell the agent the 'markdown' input is a ReceiptCal portable memory document, which adds real meaning, but it omits format/size expectations (e.g. the 70000-char limit) required to call it correctly.

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?

Specific verb ('Stage merge-only import') plus a concrete resource ('a ReceiptCal portable memory document'), and it enumerates scope (learned memories, food preferences, pantry amounts). It does not explicitly name a sibling to differentiate from (e.g. prepare_merge_food_preferences), but the scope statement is clear enough for an agent to distinguish it.

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 the use case (importing a portable memory document) and sketches the merge-only semantics, but gives no explicit when-to-use vs alternatives, no mention of the confirm_action staging step, and no conditions under which to prefer a sibling like prepare_merge_food_preferences.

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