set_vector_paths

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

No annotations are provided, so the description carries the full behavioral burden. 'Replace' hints at a destructive overwrite of prior path data, but it does not state whether the change is reversible, what permissions/auth are needed, or how existing paths are discarded. For a mutation tool with zero annotation coverage this is a meaningful gap.

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 zero filler, correctly emphasizing the replacement action and target resource. Its brevity doubles as under-specification, but that is not a structural fault.

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 mutation tool with no annotations and no output schema, the description is too thin. It omits the semantics of windingRule, the expected path-data format, and any indication of what happens to previously existing paths.

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% and neither parameter is documented in the schema. The description loosely implies the nodeId (existing VECTOR node) and vectorPaths (SVG path data), but adds no format or syntax detail for the path 'data' string or the undocumented 'windingRule' field, so it fails to compensate for the coverage gap.

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 ('Replace') and resource ('SVG path data on an existing VECTOR node'), making the mutation target unambiguous. It distinguishes itself from fill-oriented siblings like set_solid_fill and set_image_fill, though it doesn't explicitly contrast with create_vector, which produces a VECTOR node rather than mutating one.

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 when-to-use, prerequisites, or alternatives are given. The agent must infer that this applies only to already-existing VECTOR nodes and there is no routing guidance versus create_vector or other path-related tools.

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