images_trace

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

Annotations only declare destructiveHint=true; the description goes further by emphasizing the operation is irreversible and that the preset is fixed with no configuration accepted, which is valuable behavioral context. It still omits what the trace produces (a new path element?) and whether the source image is modified or retained.

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?

Two tight sentences with zero filler; the irreversible, bounded nature is front-loaded before the constraint about presets.

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?

An output schema exists so return values need no explanation, and the description adequately conveys the destructive, fixed-preset nature. But for a 5-required-parameter mutation tool, it leaves concurrency behavior (expectedRevision mismatch) and failure/permission conditions undocumented.

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% across 6 parameters, so the description carries the burden. It partially addresses preset ("bounded default preset"), but says nothing about expectedRevision (an optimistic-concurrency token), workspaceId, imageId resolution, or path semantics, leaving key parameters to raw pattern guesses.

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 (traces) on a specific resource (one local or embedded raster image) and names the mechanism (Inkscape object-trace action). This cleanly separates it from vector-oriented siblings like objects_to_paths or paths_flatten and from image siblings like images_crop/images_manage.

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?

It scopes usage by stating only the bounded default preset is available and no parameters/actions/extensions are accepted, which implies this is a rigid, one-shot operation. However, it never says when to prefer this over alternatives such as images_crop, objects_to_paths, or paths_flatten, nor does it state prerequisites.

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