set_blood_pressure

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

The description states 'Record', implying a write operation, but no annotations are provided. It fails to disclose behavioral traits like whether it overwrites existing readings, authentication needs, or error handling, leaving a significant gap for a mutation 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 a single sentence with no waste, fitting for a simple tool. However, it is overly terse and could be slightly expanded to improve clarity without losing conciseness.

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 straightforward 'record' tool, the description is minimally adequate. It lacks mention of return values (no output schema) or side effects, but the tool's simplicity means less context is needed.

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 baseline is 3. The description adds no extra meaning beyond the schema; it does not explain parameter relationships or provide examples.

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 'Record a blood pressure reading' uses a clear verb and resource, making the tool's purpose evident. However, it does not differentiate from siblings like 'get_blood_pressure' or 'delete_blood_pressure', which is acceptable given the name itself is distinctive.

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?

No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or context given. The description is too brief to offer usage direction.

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