dim_diameter

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

No annotations are provided, so the description carries full responsibility. It only states that the dimension is placed on a circle/arc by handle, but does not disclose the effect of the angle and offset parameters, what happens on invalid handles, or the nature of the created dimension entity.

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 sentence that front-loads the core purpose without extraneous details. It is concise and immediately informative.

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?

Despite the presence of an output schema, the description is too sparse for a tool with three parameters and no annotations. An agent cannot infer the meaning of angle and offset, nor the tool's behavior in edge cases, making it incomplete for reliable invocation.

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%, so the description must compensate. It explains the 'handle' parameter as the means of selecting the circle/arc, but leaves 'angle' and 'offset' completely unexplained, which is a significant gap given their defaults.

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 indicates this tool creates a diameter dimension on a circle or arc selected by handle. The resource and method are specific, and it distinguishes from sibling tools like dim_radius and dim_linear, though it lacks an explicit verb like 'create'.

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 usage for diameter dimensions on circles/arcs, but does not explicitly state when to use this tool versus alternatives such as dim_radius or dim_aligned. No exclusions or prerequisites are mentioned.

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