resinsight_well_log

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

No annotations are present, so the description alone must disclose behavior. It indicates a file export side effect, but does not explain whether files are overwritten, whether the output directory is created, whether ResInsight runs headless, or what happens on failure.

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 one efficient sentence with no filler and the key verb is front-loaded. It is somewhat under-specified, but as far as length and structure go it earns its place.

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?

This is a multi-parameter export tool with no annotations, and the description does not cover required inputs such as case_path or how properties map to LAS curves. Even with an output schema covering the return value, the missing usage context leaves an agent guessing about invocation preconditions.

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?

With 0% schema description coverage, the description needed to document or at least contextualize the five parameters, but it only implies that 'well' selects one well and that the output is LAS. The optional 'properties', 'output_dir', and 'force_software_gl' parameters receive no explanation.

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 a specific verb ('Export') and a concrete resource ('an LAS well log for one well'), making the tool's core function clear. It doesn't explicitly differentiate from siblings, but the nearest ResInsight siblings (resinsight_open, resinsight_snapshot, list_wells) are clearly different activities, so an agent can distinguish intent.

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?

There is no guidance about when to choose this tool over alternatives, nor any stated prerequisites such as needing an opened case or a valid well name. An agent must infer from the tool name and sibling list which scenario calls for this tool.

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