measure_batch

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

No annotations are provided, so the description carries the full behavioral burden. It only mentions the return type ('dict'), omitting whether the operation blocks, requires prior measurement configuration, or has side effects. The mention of a return dict is helpful but insufficient.

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 single sentence is front-loaded and concise, but it is under-specified for a 3-parameter batch tool. The return-type note adds little value because an output schema exists.

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?

Given the absence of annotations, 0% schema description coverage, and three parameters, the description is too sparse. It names the basic operation but omits parameter meaning, usage context, and behavioral expectations needed to invoke the tool correctly.

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%, so the description must compensate. It vaguely references 'items' and 'one source,' but does not explain the expected string format for items, the role of the optional source2 parameter, or the default source behavior.

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?

States a specific verb and scope: 'Measure multiple items on one source.' The 'multiple items' phrasing distinguishes it from the single-item sibling measure_item, though the term 'items' remains somewhat vague and the description does not fully differentiate it from other measurement siblings.

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?

Provides no guidance on when to use this tool versus alternatives like measure_item, measure_quick, or measure_statistics_item. The batch nature implies a use case, but the description never states it explicitly.

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