measure_dihedral

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 simply states 'Measure the dihedral (degrees)' without mentioning potential side effects (e.g., creating a measurement object in the session), ensuring valid selections, or read-only nature. This is insufficient for an AI agent to predict the tool's full 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 a single sentence that is clear, front-loaded, and contains no extraneous information. Every word earns its place by specifying the action, unit, and selection requirements.

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?

The description covers the essential aspects for a simple measurement tool: what is measured, in what unit, and the parameter requirements. The existence of an output schema presumably documents the return value. However, the lack of any side-effect disclosure or annotation guidance leaves a small gap in completeness.

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 coverage is 100% and each parameter description already says 'Single-atom selection,' so the schema handles parameter meaning. The tool description adds minimal extra value by reinforcing that the four parameters define the dihedral, but it does not provide additional syntax or semantic context beyond what the schema already documents. Baseline of 3 is appropriate.

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 'Measure' with the resource 'dihedral' and specifies 'degrees' and 'four single-atom selections,' clearly distinguishing it from sibling measurement tools like measure_distance and measure_angle. The purpose is unambiguous and actionable.

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 dihedral measurements via the phrase 'defined by four single-atom selections,' but it does not explicitly state when to use this tool versus alternatives like measure_distance or measure_angle. No exclusions or alternative references are provided, so usage guidance is implied rather than explicit.

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