create_measurement

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action of creating a measurement line and that it shows distance. It does not disclose side effects, whether it mutates the document, how it behaves with invalid node IDs, or what the resulting line looks like.

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, clear, front-loaded sentence with no unnecessary filler. Every word contributes to understanding the tool's core function.

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 relatively simple tool with complete schema coverage, the description is mostly adequate. However, with no output schema and no annotations, it lacks detail about what happens after creation, such as whether the measurement line is selected, whether it is visible immediately, or how distance is displayed. Sibling alternatives are also not addressed.

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 100%, so the input schema already documents all three parameters adequately. The description adds minimal value by linking the two nodes to the measurement line, but it does not explain node ordering or how 'direction' affects the result beyond the schema's enum and default.

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 states a specific verb and resource: 'Create a measurement line between two nodes showing distance.' This clearly describes the tool's function. However, it does not explicitly distinguish itself from the sibling tool 'measure_distance' or 'create_line', though the term 'measurement line' provides reasonable implicit differentiation.

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 the tool is used when a visible measurement line between two nodes is needed, but it provides no explicit guidance about when to use it versus alternatives like 'measure_distance' or 'create_line'. No when-not-to-use or alternative-selection criteria are given.

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