create_measurement

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only says 'Create a measurement line showing distance' but omits details such as whether nodes are modified, whether the line is a permanent object, visibility conditions, or permission requirements. The description does not contradict any annotations since none exist.

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, concise sentence that directly states what the tool does without any extraneous words. It is front-loaded and efficient.

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 tool with 3 parameters and no output schema, the description is minimally adequate but lacks completeness. It does not specify what the tool returns (e.g., a reference to the created measurement line), nor does it explain any side effects or constraints. Given the simplicity, a 3 is fair.

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 input schema has 100% coverage with descriptions for all three parameters (nodeId1, nodeId2, direction). The tool description does not add new parameter semantics beyond the schema, but that's acceptable given the high schema coverage. Directions like 'AUTO' are self-explanatory; no extra explanation needed.

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's purpose: creating a measurement line between two nodes that shows distance. It uses a specific verb and resource, and it distinguishes itself from sibling tools like 'measure_distance' (which likely just returns a numeric distance) or 'create_line' (generic line).

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 provides no guidance on when to use this tool vs. alternatives. Sibling tools include 'measure_distance' which might be used for numeric distance without creating a visual line, and 'create_line' for generic lines. No context is given for appropriate use cases or prerequisites.

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