measure

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

With no annotations, the description carries the full burden. It discloses output-oriented behavior, including notes like 'scale not applied' or 'negative scale', but does not state that this is a read-only measurement operation, nor does it mention permissions, side effects, or mutation risk.

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 three sentences and front-loads the returned metrics before usage guidance and the sibling alternative. It is compact and free of obvious filler, though the opening list is more output inventory than purpose statement.

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?

There is no output schema and no annotations, so the description must cover both behavior and return values. It lists several return fields and usage context, but omits the required `names` input semantics and does not explain whether results are per object or how they are structured.

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 0% for the sole required parameter `names`, and the description never mentions the parameter, its multiplicity, or what object names it expects. It does not compensate for the missing schema documentation.

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 enumerates the measured quantities (world-space size, min, max, center, origin position, rotation, scale) and explicitly distinguishes the tool from measure_profile. It implies measuring an object, but lacks an explicit verb+resource statement such as 'Measure one or more objects'.

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?

It gives clear context with 'Use it after every move' and names the alternative for reference images: measure_profile. It does not state when not to use this tool or any prerequisites, but the primary usage condition is clear.

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