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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so safety is partly covered. The description usefully adds that the result is a NEW path (the source path is not restated as modified) and that the offset can go inward or outward, but it does not say what happens to the original shape, whether the operation can fail, or how the offset handles self-intersecting geometry.

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?

A single front-loaded sentence with no filler. It is efficient, though the one sentence could have absorbed a clause on sign convention for 'distance' at little cost.

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 two-parameter geometry mutation with no output schema and no parameter documentation, the description omits critical details: the meaning/sign of distance, what shape_id refers to, and whether the source path is preserved. An agent could easily call this with the wrong sign and invert the result.

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% for both parameters, so the description must carry the burden and largely fails. It implies that 'distance' encodes offset magnitude and direction, but never says whether a negative value means inside versus a separate flag, and shape_id is not explained at all (target path identifier).

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 names a specific verb ('Draw a new path') and a specific geometric operation ('at a set distance outside or inside a path'), which is clearly distinct from sibling operations like edit_path, create_path, and smooth_path. It is clear what it does, though it never names those siblings or states its relationship to them.

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?

There is no guidance on when to choose this over create_path, edit_path, or clip_shapes, and no prerequisites or constraints are mentioned. The 'outside or inside' phrase hints at a use case but leaves the agent to infer the selection condition.

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