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

Goes beyond annotations by disclosing the external PNG.now dependency, the optional synchronous waiting behavior, and important SSRF/security rejections (private-network URLs, embedded credentials). It does not cover auth, rate limits, or cost implications, but with annotations and an output schema present, this is solid added context.

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?

Two tight sentences: the first front-loads the operational flow and the second front-loads safety constraints. No filler or repetition.

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?

Covers the core conversion flow and URL safety, but a 9-parameter tool with zero schema descriptions needs more parameter meaning. It also does not explain how the 'don't wait' path connects to get_conversion_status, leaving an agent to infer polling behavior.

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 0% across 9 parameters; the description only clarifies source_url (public, no credentials) and hints that converter is a slug. Width, height, quality, strip_metadata, background_color, timeout_seconds, and wait_for_completion are entirely undocumented, so the description fails to compensate for the schema gap.

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 multi-step action: download a remote PNG/usable image URL, submit it to PNG.now with a converter slug, and optionally wait. The conversion-creation scope is distinguishable from siblings like get_conversion_status and list_converters.

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?

The 'optionally wait for the result' phrasing implies you can poll later, and URL restrictions are stated, but the description never explicitly says when to use this tool versus get_conversion_status or list_converters. Usage is implied rather than directed.

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