clear_measurements

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does this well by explaining that reading measurements enables Result view items, that they accumulate over time, and that re-measuring restores cleared items, which characterizes the tool's side effects and reversibility.

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 three short sentences with the core action front-loaded in the first sentence. The following two sentences provide valuable behavioral context without filler, repetition, or unnecessary detail.

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 zero-parameter tool with no output schema and no annotations, the description is complete: it defines the action, explains why the action is needed, and tells the agent how to restore cleared items. Nothing essential is missing for correct invocation.

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?

The tool has zero parameters, so the schema already provides complete coverage. The description correctly does not attempt to document parameters that do not exist, and a baseline of 4 is appropriate for a parameterless tool.

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 opens with a precise verb 'Remove' and a clear object: 'all measurement items from the on-screen Result view.' It also explicitly differentiates itself from the sibling 'measure' tool by explaining that measure enables items on the Result view, so the agent can tell what this tool does and how it relates to nearby tools.

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 explains the accumulation behavior triggered by measure and states that this tool clears all items, which gives clear context for when to invoke it. It does not explicitly list exclusions or alternative tools, but no other sibling appears to serve the same clearing purpose, and the measure context provides sufficient guidance.

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