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

Adds valuable behavioral context beyond annotations: 3 credits consumed, sensitive-tier approval workflow (from-now-on vs just-once), first-use manager approval, and the fact that output is native SVG with editable paths. It does not explain why annotations mark it destructiveHint:true, but nothing in the description directly contradicts the annotations.

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 tightly organized: function sentence, differentiation and use cases, routing rule, and approval pragmatics each in their own block. No filler exists; every line carries operational information an agent needs.

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 generation tool with a complete schema and annotations, it covers what the tool does, when to route to it, output type, credit cost, and approval behavior. It is slightly less complete around side effects (why destructiveHint is true) and the relationship between the two folder-related parameters is left to the schema, but these are minor 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 100%, so all six parameters are already documented, including prompt style guidance and the folder vs folder_name distinction. The tool description itself does not add per-parameter semantics beyond the schema, so it stays at the baseline without compensating or hurting.

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 precise action ('Generate a native SVG vector image using Recraft V4 Pro Vector'), names the output type ('true SVG with editable paths'), and lists concrete use cases: logos, icons, brand marks, vector illustrations, and scalable graphics for Framer animations. The claim of being the only tool that outputs true SVG clearly differentiates it from sibling generation tools.

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?

Provides an explicit routing rule: 'SVG/vector/logo/icon/brand mark/scalable graphics → use this', plus a credit-cost tag. The 'ONLY tool that outputs true SVG' sentence makes the selection criterion explicit against alternatives. An agent can determine when to invoke this tool without ambiguity.

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