Add images to project

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

Discloses that images are downloaded to '<project>/public/images/' and how to reference them, adding behavioral context beyond annotations. Does not mention overwrite behavior or error handling.

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 sentences, front-loaded with the core action, no redundant information. Efficient and clear.

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?

Provides usage guidance for the tool's output (referencing in content.json) but lacks mention of prerequisites (e.g., project existence) and error scenarios. Adequate for a simple tool.

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?

Description explains the 'images' parameter (url from search results, short filename) but omits explanation of the 'slug' parameter, leaving it unclear. With 0% schema coverage, this is a partial compensation.

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 it downloads Wikimedia images into a specific project directory, distinguishing it from sibling tools like search_wikimedia_images and preview_images.

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?

Implies usage via 'Pass the direct URLs from search results', guiding the agent to use search results first. However, it does not explicitly state when to use this tool vs alternatives like preview_images.

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