input_B

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

Since no annotations are provided, the description carries the behavioral disclosure burden. It appropriately conveys that this is a convenience wrapper and describes the data scope, but it does not explicitly state read-only behavior, return format, or potential side effects. This is a moderate gap for a getter 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 two concise sentences with no redundancy. The primary action is front-loaded, and the convenience equivalence is stated efficiently without wasting words.

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?

With no annotations, no output schema, and no parameter explanations, the description omits important details needed to call the tool correctly, especially the meaning of 'imag' and the expected return structure. It is adequate for basic orientation but incomplete for confident invocation.

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%, and the description does not explain either parameter. 'input_path' is partially inferable as the path to an Input, but 'imag' is completely unexplained. The description does not compensate for the lack of schema field descriptions.

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 retrieves both measured and simulated data from an Input, using a specific verb and resource. It also distinguishes itself by noting the 'msb=B' equivalence and the convenience-method nature, which differentiates it from siblings like input_M or input_get_data.

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 gives a clear usage context: use this when you need both measured and simulated data, or as a shortcut for get_data(msb='B'). It does not explicitly mention when not to use it or name alternatives such as input_M or input_S, but the intent is reasonably clear.

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