create_arc

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

No annotations are present, so the description must disclose behavioral traits. It only states 'create an arc,' without mentioning side effects, mutation aspects, or how it integrates with existing geometry. The description is minimal.

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 very short (one sentence), making it concise, but it lacks structure. Important details like default angles and segments are not front-loaded. A bit more structure would improve clarity.

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 9 parameters and no output schema, the description is incomplete. It doesn't explain how the arc is created (e.g., in the active model), what happens to existing entities, or the return value. Important context is missing.

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 78%, so most parameters are already described in the schema. The description adds little beyond what the schema provides, only repeating 'center, radius, start/end angles.' It does not clarify default behaviors or units beyond degrees.

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 it creates an arc in SketchUp and mentions key parameters (center, radius, angles). This distinguishes it from sibling tools like create_circle (full circle) or create_polygon (polygon).

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 on when to use this tool vs alternatives, or when not to use it. It does not mention prerequisites or context, such as whether an active model or entity is needed.

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