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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety and repeatability are covered. The description adds the semantic distinction that confirm=true accepts an assumption unchanged while answer text overrides it, which is useful, but it does not say what happens on invalid input (both supplied, neither supplied, unknown id).

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?

Three short sentences, front-loaded with the action and followed by the mode rule. Minor redundancy between the opening sentence and 'answer text answers a question or corrects an assumption', but nothing is wasted.

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 needn't be described, and annotations cover the mutation profile. Still, for a four-parameter mutation tool with zero schema descriptions, the unexplained required 'dimension' parameter and vague 'id' leave a real gap in what an agent needs to call it 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 coverage is 0%, so the description must carry parameter meaning, and it only covers answer and confirm — though it does add genuine value by declaring they are mutually exclusive, which the schema does not encode. The required parameters id and dimension are never explained at all, leaving an agent unable to know what dimension refers to.

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?

States a specific verb and resource ('Record the person's answer') and separates the two modes: answering a question versus confirming/correcting an assumption. It doesn't differentiate itself from siblings like grill_skip or grill_gaps, but the action itself is unambiguous.

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?

'Give exactly one' gives a real selection rule between the answer and confirm parameters. However, it says nothing about when to call this versus grill_skip or grill_gaps, or what preconditions exist (e.g., must a grill session be active).

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