Delete Blood Pressure

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

The destructiveHint annotation already flags that this is destructive; the description adds the relevant workflow detail that the version ID should be obtained from get_blood_pressure /all. It does not cover permanence or side effects, but annotations lower the burden and there is no contradiction.

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 short sentences with the main action first and the lookup guidance second; no filler or repeated schema content.

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 simple two-parameter delete operation with destructive annotations and no output schema, the description is sufficient: it identifies the target, explains how to find the required version, and relies on the schema for parameter formats. It could mention irreversibility, but destructiveHint already communicates this.

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?

Input schema covers both parameters with 100% coverage (date format and version/ID descriptions). The description adds a small contextual hint that the version comes from a get_blood_pressure lookup, but does not need to restate parameter details.

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?

Description states exactly the action ('Delete a blood pressure reading') on a specific resource, and differentiates from sibling get_blood_pressure and set_blood_pressure. It also names the lookup endpoint needed to identify the target.

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 provides an explicit prerequisite workflow: use get_blood_pressure with the /all endpoint to find the version ID. It doesn't explicitly state when not to use this tool, but for a deletion it is clear enough; no alternative deletion tool exists among siblings.

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