set_blood_pressure

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

No annotations are provided, so the description must communicate behavior. It only states that blood pressure values are set, without disclosing side effects, whether this updates an existing entry, expected units, validation, or any prerequisites. This is a significant gap for a mutation-oriented tool.

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 short and front-loaded with the main purpose, followed by a clean Args list. Every line is reasonably purposeful, though the parameter descriptions add only a little beyond the parameter titles.

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 write tool with no annotations, the description is incomplete. It lacks usage context, behavioral details, units, and any indication of side effects or constraints. An agent could call it with plausible values but would not know whether it creates or updates a record or what the expected ranges are.

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 0%, but the description provides brief definitions for all four parameters: systolic, diastolic, pulse, and notes. This is helpful but minimal, lacking units, acceptable ranges, and any indication of how the notes field is used.

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 specific verb and resource, 'Set blood pressure values', which clearly states the action and target. It is easily distinguished from siblings like get_blood_pressure and the various set_activity_* tools because it is the only one targeting blood pressure with a write 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?

There is no guidance on when to use this tool versus alternatives. It does not say whether it creates a new reading, overwrites existing data, or requires a date/time, and it names no alternative tools or conditions for using them.

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