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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive), but the description adds meaningful behavior: the camera opens inside the chat, the user performs the capture, and the downstream read/log steps happen after. It doesn't say what happens if the user cancels or whether the call blocks until a photo appears, which would complete the picture.

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?

Two sentences, front-loaded with the triggering condition, then the mechanism, then the exclusion. No filler or repetition of the title.

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?

An output schema exists so return values need not be explained, and the description covers the trigger, the handoff flow, and the alternative. Minor omissions are post-invocation behavior (cancel, timeout, or whether the tool returns before a photo exists).

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% and the single optional "note" parameter is fully documented in the schema as "Anything they said about the meal, for the read." The description adds nothing about the parameter, so the baseline of 3 applies.

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 names a specific verb+resource ("Opens the Almost Fire camera in the chat") and explains the outcome chain: the person takes or chooses a photo, "Stoke reads each food with its grams and calories, and Log saves it." This is clearly distinguishable from the photo-reading siblings it names.

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?

It gives both a positive trigger ("wants to log a meal from a photo but hasn't attached one, or the app can't hand you their photo") and an explicit exclusion with a named alternative ("Do not use when they've attached a photo; use read_meal_photo"). The only gap is that sibling read_meal_photo_upload goes unmentioned, so the boundary between the two read paths is slightly ambiguous.

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