path_operation

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

With no annotations, the description carries the full burden and does disclose useful behavior: which object's id/style/layer survives per operation and that `result` lists the output ids. However it omits preview semantics (dry-run?), required permissions, and failure behavior across the 12 operations.

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?

Purpose is front-loaded, but the body is a dense run-on mixing per-operation outcome rules, a stray '(E22)' reference, and a return-value note mid-stream. Every sentence is relevant, yet the ordering is scattered.

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 mutating, multi-operation tool with no annotations and no output schema, the description covers outcome semantics better than most, but the unexplained preview flag and absent error/permission behavior leave real gaps.

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%, so the description must compensate. It explains a few operation values (difference, to_path, combine) but leaves ids, doc_id, and preview entirely unexplained, and the enum's other operations (division, cut, break_apart, simplify, flatten) unaddressed.

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?

States a specific verb+resource: Inkscape geometry operations applied to object ids, and names concrete operations (difference, union, to_path) that make the tool distinguishable from element-manipulation siblings like add_elements or z_order. It does not explicitly contrast itself with siblings, but the domain is unmistakable.

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?

The description explains what certain operations do but never says when to choose this tool versus alternatives (e.g. split, run_actions) or when a given operation is appropriate. No prerequisites or exclusions are given.

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