set_wallpaper

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context of its own: it doesn't say what happens with an invalid or non-existent path, whether the wallpaper persists across restarts, or whether animated images are handled.

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?

A single front-loaded sentence with zero filler. It is efficient, though the terseness is part of why non-obvious behaviors go unstated.

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 one-parameter tool with full schema coverage and annotations, the description is minimally sufficient to invoke correctly. It still leaves failure modes and persistence behavior unexplained, which matters for a mutation of the desktop state.

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?

With a single parameter at 100% schema coverage, the schema already specifies 'Absolute path to image file'. The description restates 'specific image file path' without adding format constraints or examples, so the baseline 3 applies.

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 pairs the specific verb 'Set' with the resource 'wallpaper' and the target 'specific image file path', which is unambiguous. It is not explicitly distinguished from siblings like next_wallpaper/prev_wallpaper or set_theme, but the phrase 'specific image file path' implicitly contrasts with cycling tools.

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?

There is no guidance on when to prefer this over next_wallpaper, prev_wallpaper, list_wallpapers, or set_theme. Nothing states prerequisites such as the file needing to exist or being a supported image format.

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