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

Beyond the light annotations (readOnlyHint, openWorldHint=false), the description discloses pricing (0.08 USDC on Base), explicitly disclaims performing analysis, signing or charging, describes the return payload (canonical endpoint, supplied input, payment instructions), and notes validation behavior (preserves native curves, rejects unsupported constructs and EPS transforms). This is a rich behavioral profile for a preparation tool.

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?

Four compact sentences front-load purpose, then cost, then non-actions, then behavioral constraints, with no filler. The one weakness is the leading 'Inspect', which is slightly at odds with the later disclaimer that no analysis is performed.

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?

With no output schema, the description appropriately explains what the tool returns and what it does not do, and it covers cost and input validation. The main omission is any explanation of the 'minSegmentMm' parameter, which an agent would need in order to supply it correctly.

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 only 33%, and the description provides no guidance for the undocumented parameters. The 'format' enum is only obliquely referenced via 'SVG or restricted CorelDRAW EPS', and 'minSegmentMm' is completely unexplained in both schema and description despite being a numeric constraint on analysis granularity.

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 states a specific action ('Prepare a paid HTTP request') and resource scope ('original SVG or restricted CorelDRAW EPS curve commands'), and it distinguishes itself from the sibling prepare_vector_health by emphasizing native Bezier curves and rejection of EPS transforms. The opening verb 'Inspect' slightly muddies the purpose, since the tool explicitly does not perform inspection or analysis, but the rest of the sentence clarifies it.

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?

Usage is implied through input constraints ('original SVG or restricted CorelDRAW EPS', 'rejects unsupported constructs and EPS transforms'), giving an agent a reasonable sense of when this tool applies. However, it never names the alternative sibling prepare_vector_health or states explicitly when to choose one over the other, leaving routing to inference.

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