dim_radius

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

With no annotations available, the description carries the burden of disclosing effects. It explains parameter meanings but does not state that the tool modifies the drawing by adding a dimension object, nor does it mention any prerequisites beyond 'by handle'. It is not contradictory, but lacks explicit behavioral transparency.

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?

One sentence with no filler. All content is relevant, and the key information is front-loaded.

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?

With an output schema present and a simple 3-parameter tool, the description covers the essential usage. It could be improved with an explicit mutation statement, but is adequate for the tool's complexity.

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 descriptions are absent (0% coverage), so the description compensates by explaining angle ('where it points') and offset ('leader length factor'). The 'handle' parameter is only implied as the target entity, so not fully explicit.

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?

Description clearly identifies the tool as creating a radius dimension on a circle/arc using an entity handle. It distinguishes from sibling dimension tools (dim_diameter, dim_linear) by specifying 'radius' and 'circle/arc'. However, it lacks an explicit verb such as 'Creates' or 'Adds', relying on the noun 'dimension'.

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?

States the target entity type ('circle/arc') and the mechanism ('by handle'), giving clear context for when to use. It does not explicitly mention alternatives or when not to use, but the specific 'radius' scope provides implied guidance relative to other dimension tools.

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