measurements_delete_head_circumference

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose a key trait: 'This action is permanent,' which signals irreversibility. However, it does not mention lower-level details such as permission requirements, potential cascading effects, or what happens to dependent data. For a destructive operation, the permanence disclosure is valuable but not exhaustive.

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 short sentences, with the core action and resource front-loaded. There is zero redundant wording, and it avoids repeating schema details. Every word contributes to the core message.

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 single-parameter, destructive tool with an output schema present, the description covers the essential facts: what it operates on and that it is irreversible. The lack of usage guidance is a minor gap given the simplicity and clarity of the operation, and the output schema handles return-value documentation.

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%, and the parameter's own description ('ID of the head circumference record to permanently delete') already conveys its meaning. The tool description adds no additional detail about the parameter's format, validation, or behavior. Baseline 3 is appropriate since the schema does the heavy lifting.

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 states a specific verb ('Delete') and a specific resource ('head circumference record'), which clearly distinguishes this tool from the many sibling delete tools for other measurement types (e.g., measurements_delete_bmi, measurements_delete_height). The action is unambiguous and matches the schema's head_circumference_id parameter.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or situations where a different action (e.g., update instead of delete) would be appropriate. The only context is the permanent nature of the deletion, which is a cautionary note but not usage direction.

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