load_measurement_files

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 mentions the side effect of loading into REW and that it returns measurements, but does not state whether existing measurements are affected, path handling beyond forward slashes, or failure/error behavior.

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 highly concise, using two sentences to state the action, scope, and return value. It is front-loaded with the primary verb and resource, with no redundant information.

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 load tool, the description covers the core function but is thin given the lack of annotations and output schema. It omits usage context, side-effect details, and error conditions, making it minimally viable but not comprehensive.

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 schema provides 100% coverage for the single `paths` parameter, so the baseline is 3. The description adds the .mdat file format detail, clarifying the expected input beyond the schema's generic 'file paths' description.

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 clearly states the tool loads .mdat measurement files into REW and returns the measurements that appeared. It is specific as to the resource (REW measurements) and action (load), and distinguishes itself from import_* tools that handle different data formats.

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 implies usage for loading .mdat files, but provides no explicit context for when to use this tool versus alternatives like import_frequency_response or read_measurement. No exclusions or alternative recommendations are given.

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