transform_elements

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

With no annotations, the description should fully disclose behavior but only partially does. It describes operations and mentions saving the result, but it does not clarify whether the tool overwrites files, requires permissions, or handles errors. Key behavioral traits like file modification are ambiguous.

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 concise and front-loads the purpose. The list of operations is compact, though the abbreviations could be clearer. Overall, it is economical with words.

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 complexity of 5 parameters, no schema descriptions, no output schema, and no annotations, the description is incomplete. It lacks details on input/output paths, error conditions, and default behaviors, leaving gaps for an agent.

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 coverage is 0%, so the description must explain parameters. It covers operation (with examples), ids (usage note), and options (example). However, svg_path and output_svg_path are not described at all, missing essential semantics.

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 'Apply an Ink/Stitch conversion to SVG elements and save the result.' It lists specific operations and distinguishes itself from siblings like list_elements and set_element_params.

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 mentions that ids is required for all but jump_to_stroke and suggests getting them from list_elements. However, it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it.

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