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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: it performs no vectorization itself and consumes no credits, plus describes the interactive hand-off flow. It stops short of noting any UI-state or auth prerequisites.

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?

Front-loads the usage condition and follows with the behavior and the exclusion, so the agent gets routing info first. The opening sentence is somewhat run-on with its parenthetical, but every clause carries information and nothing is padding.

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 zero-parameter, read-only UI-opening tool with full annotation coverage and no output schema, the description supplies everything needed: when to call it, what it does not do, and the credit implication. Nothing required for correct invocation is missing.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies no arguments are supplied by the caller.

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 action (opens the Shapesoda window), the resource (the editor UI), and what the user does there (picks the file, sees the vector result, adjusts it). It explicitly distinguishes itself from the vectorize sibling by declaring 'Does not vectorize by itself,' so an agent can route without opening either schema.

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?

Gives an explicit trigger condition ('when the user wants to vectorize an image but you cannot pass the image to vectorize'), enumerates the specific blocking cases (no image, upload_id, or exact base64 bytes), and names a negative case ('Do not use for generating new images'). The when and when-not are both spelled out.

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