sketch_offset

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create offset curves' without explaining side effects (e.g., whether original entities are preserved), permissions required, or behavior on invalid input. The description is too brief to inform the agent about important traits.

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 concise sentence, efficient and front-loaded. However, it may be slightly under-specifying given the tool's complexity (5 parameters). A balance of brevity and completeness would merit a 5, but here the brevity omits necessary details.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the workflow (e.g., need an active sketch), what types of entities are eligible, or how the offset algorithm works. The agent lacks necessary context to use the tool effectively.

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 schema already documents all parameter meanings. The description adds no additional context beyond the parameter descriptions. It does not clarify interactions between parameters (e.g., how 'side' relates to 'distance' direction). Baseline 3 is appropriate.

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 verb 'Create' and resource 'offset curves from sketch entities', distinguishing it from other sketch creation tools like sketch_line or sketch_circle. However, it could be more specific about the operation's effect (e.g., adding new curves) to differentiate from modification tools.

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 on when to use this tool versus alternatives. Sibling tools include many sketch creation and modification tools, but the description does not mention any prerequisites, limitations, or when not to use this tool. For example, it doesn't clarify that the sketch must be active or that the tool adds new curves rather than modifying existing ones.

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