delete_measurement

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

With no annotations provided, the description carries full burden for disclosing behavior. It explicitly states that there is no confirmation and no undo, and that REW deletes immediately, which is critical for a destructive operation. It does not cover permissions or side effects, but the most important behavioral trait is well-disclosed.

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 two sentences, front-loaded with the action and resource. The second sentence adds essential warning about irreversibility without any wasted words.

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?

The tool is simple (one required parameter, no output schema), and the description plus schema cover its core usage and the critical destructive behavior. It could mention what happens on invalid input or whether deletion is permanent across sessions, but the essential context is present, making it sufficiently complete for this 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 description coverage is 100%, so the schema already documents the measurement parameter well (UUID preferred or 1-based index). The tool description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is 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 the verb ('Delete'), the resource ('one measurement from REW'), and the scope ('one measurement'). It distinguishes the tool from sibling tools like rename_measurement and get_measurement by naming the specific action.

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 implies usage for deleting a measurement but does not explicitly state when to use it over alternatives or when not to use it. The warning about no undo suggests caution, but there is no mention of exclusions or alternative tools for safer deletion.

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