sw_measure

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

The readOnlyHint=true and destructiveHint=false annotations already establish this as a safe read operation. The description adds useful behavioral context by implying a non-mutating measurement analogous to SolidWorks' Measure tool, but it does not mention return format, units, or failure conditions.

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 definition is a single front-loaded sentence with no wasted words. The mode mapping is compact and immediately useful.

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 schema documents the Entity structure and the doc default, annotations cover the safety profile, and the description explains the measurement modes. The main remaining gap is that output units/format are not described, which is a limitation given there is no output schema.

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 50% schema description coverage, the description compensates partially by mapping the entity count to measurement types: one entity for length/area/diameter, two for distance/angle. It does not add detail about the doc parameter or the Entity fields, which are left to the schema.

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' and names the resources and modes: distance/angle between two entities and length/area/diameter of one. It is clear what the tool does, though it does not explicitly distinguish itself from nearby tools such as sw_mass_properties.

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 phrasing implies that one entity yields length/area/diameter while two entities yield distance/angle, which helps select the right measurement mode. However, it does not state when not to use the tool, nor does it name alternatives or prerequisites.

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