download_and_convert_images

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

Annotations already signal side effects (destructiveHint=true, readOnlyHint=false), so the description appropriately doesn't repeat safety warnings. It adds useful specifics like saving to a target directory and returning a local path, but doesn't disclose overwrite behavior or failure scenarios, which is a minor gap beyond 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 compact (two sentences), front-loaded with the primary action, and every phrase adds value. No filler or redundancy.

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 simple tool with well-documented parameters and no output schema, the description adequately covers the return value and main behavior. It could mention error handling or edge cases, but given the tool's simplicity and the presence of annotations, it is sufficiently complete. A 4 reflects that minor behavioral details are 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 input schema has 100% coverage with descriptive text for both url and outputDir. The description mentions target directory and absolute local path, but these echo the schema without adding significant new meaning. Baseline 3 is appropriate.

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 clearly states the tool's action (downloads an image, converts it to PNG), the resource (image from a URL), and the output (saves to a directory, returns absolute local path). This specificity distinguishes it from all sibling browser tools, which are unrelated to image processing.

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 description provides a clear context: use this tool when you need to download an image and convert it to PNG, saving it locally. It doesn't explicitly mention alternatives or exclusions, but the context is unambiguous given the tool's unique function among siblings.

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