Diameter Dimension

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

The description indicates it's a 'create' operation, consistent with the readOnlyHint=false annotation. However, it provides no additional behavioral context such as side effects, permissions, or error 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?

Single sentence, front-loaded with action and example. Every word earns its place.

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 tool with 11 parameters and an output schema, the description is adequate but could mention prerequisites (e.g., existing circle), or common use cases.

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 description doesn't need to add much. The tolerance example hints at the fit parameter but doesn't explicitly link to schema fields.

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 states the tool creates a diameter dimension for a circle, with an example of tolerance. It distinctly differentiates from sibling tools like dimension_radius, dimension_linear, etc.

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?

Usage context is implied (for circles requiring diameter dimension) but no explicit guidance on when to use this versus alternatives like dimension_radius for arcs or circles with smaller radii.

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