save_all_measurements

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

With no annotations provided, the description carries the full transparency burden. It discloses the key side effect that the tool overwrites an existing file, which is critical for an agent to know. However, it does not mention other behavioral aspects such as whether it requires loaded measurements, what happens if the path is invalid, or what the tool returns after saving.

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 extremely concise, consisting of just two short sentences. It front-loads the main action ('Save every loaded measurement to a single .mdat file') and then immediately states the overwrite behavior and path formatting. Every word earns its place with no filler.

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 tool with only two parameters and no output schema, the description provides enough context for agent selection and invocation. It explains the tool's scope, the destructive overwrite behavior, and the required path format. It could be slightly more complete by mentioning the optional note parameter or return behavior, but given the tool's simplicity, it is sufficiently complete.

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?

The input schema already provides 100% coverage with descriptions for both parameters ('path' and 'note'). The description adds minimal parameter-specific value; it repeats the forward-slash requirement already present in the schema and does not elaborate on the optional 'note' parameter. Since schema coverage is high, the baseline of 3 applies.

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 uses the specific verb 'Save' with the resource 'every loaded measurement to a single .mdat file', making the tool's action and scope unmistakable. It also distinguishes itself from sibling measurement tools by focusing on the save-all-to-one-file behavior, and the parenthetical '(overwrites an existing file at that path)' adds important clarifying detail.

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 clearly implies when to use the tool (when saving all loaded measurements to a single file) but does not explicitly discuss alternatives or when not to use it. It does mention the requirement to use forward slashes, which is useful, but there is no explicit 'use this instead of X' guidance.

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