assert

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

The annotations already convey that the operation is read-only, idempotent, and non-destructive, and the description does not contradict them. However, the description adds no additional behavioral context, such as what happens when the assertion fails, what scope the check covers, or any subtle side effects.

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, front-loaded sentence with no filler or redundant wording. It is efficient, though its brevity contributes to the ambiguity penalized in other dimensions.

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?

Although annotations and an output schema reduce the burden, an agent still lacks essential context: which operation the assertion applies to, how path and equals interact, and what 'measured value' means in the Mastercam domain. This is insufficient for a tool with three parameters and no parameter-level descriptions.

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 0% schema description coverage, the description must compensate by explaining the parameters, but it only hints at the concept of 'expected value' (equals) and 'measured value' (path). It does not clarify that path identifies where the measured value comes from or what operationId refers to.

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 clear action: verifying that a measured value matches an expected value. It is more informative than the bare name 'assert', but 'measured value' is somewhat vague and it does not explicitly distinguish itself from similar sibling tools like verify_change or inspect.

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?

No guidance is given for when to use this tool versus alternatives such as inspect, measure, or verify_change. There are no conditions, prerequisites, or exclusions, so the intended usage must be inferred from the tool name and schema.

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