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

Adds substantial context beyond annotations: the operation is free, the link is one-time and expires in 10 minutes, and the response includes a ready-to-run curl command. The annotations only cover safety profile (non-read-only, non-destructive, non-idempotent), so the expiry/one-time semantics are genuinely new and decision-relevant information.

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?

Three compact sentences with the key facts front-loaded: cost, return value and lifecycle, then next step, then applicability/alternative. No sentence is redundant.

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?

No output schema exists, and the description compensates by describing exactly what is returned (one-time link, 10-minute validity, curl command) and what to do with it. For a one-parameter setup tool, this is complete enough to invoke without further exploration.

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 100% and there is only one optional parameter, so the schema already documents file_name fully. The description implies the file is local and becomes the result name, but adds no format or constraint detail beyond what the schema states. Baseline 3 is appropriate given the schema does the work.

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+resource: returns a one-time upload link plus a curl command for sending a local image. It explicitly distinguishes itself from upload_logo (chat apps) and names vectorize as the downstream step, so an agent can route correctly without opening the 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 applicability condition ('For coding agents that can reach mcp.svgproof.com from their shell') and an explicit exclusion with the alternative to use instead ('in a chat app use upload_logo instead'). It also states the required follow-up call (vectorize with the upload_id), leaving nothing to inference.

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