set_line_completion

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

With no annotations provided, the description fully discloses behavioral traits: the toggle mechanism (fetches current state, toggles only if needed), non-idempotence, and retry warning. This gives the agent crucial safety information.

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 concise with three sentences: purpose, mechanism, and critical warning. Every sentence adds value, and the most important information (purpose) is front-loaded.

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?

Given the tool's simplicity (boolean toggle, no output schema), the description is mostly complete, covering purpose, behavior, and a key warning. It lacks return value info, but that is a minor gap for this type of 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 100% (both parameters have descriptions: 'Line UUID token' and 'Desired completion state'). The description adds no extra parameter detail beyond what is in the schema, making the baseline score of 3 appropriate.

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 that the tool marks a shopping note line as completed or uncompleted, using a specific verb ('Mark') and resource ('shopping note line'). It distinguishes itself from sibling tools (add/change/delete line) by focusing on completion state toggling.

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 provides important usage guidance: it explains the toggle endpoint behavior and explicitly warns against retrying on timeout due to non-idempotence, instructing to check current state first. It does not explicitly state when not to use or list alternatives, but the guidance is clear and actionable.

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