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

No annotations are provided (all false), and the description does not mention side effects, permissions, whether it modifies the original creation, or any behavioral details. The description only states the action without transparency.

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 very short but the second sentence is cryptic and could mislead. It could be clearer without being verbose, so it is acceptable but not excellent.

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?

The description does not mention the output format (SVG), what a 'raster creation' is, or any prerequisites. It lacks context about how this tool fits into the workflow, making it incomplete.

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?

The schema has no descriptions for folderReference or creationIdentifier, and the tool description does not explain them at all. There is zero information about what these parameters mean, so the description fails to compensate.

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 gives a verb 'trace' and target 'SVG', but the second sentence referencing a sibling tool mixes two actions and creates ambiguity about whether it converts an existing raster or generates a new vector. It is not fully clear.

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 mentions using `images_generate_svg` for new vector from prompt, which helps differentiate from this tracing tool. However, it does not explicitly state when to use this tool versus other alternatives; it only implies the distinction.

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