next_wallpaper

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

Annotations already declare this as non-read-only, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds that the change is confined to the current theme's rotation, but it omits behavior at the end of the rotation (wrap-around or error), side effects, and any return confirmation.

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; every phrase (verb, resource, rotation scope) carries information.

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 zero-arg, non-destructive action with annotations carrying the safety profile and no output schema, the description is nearly sufficient. The one real gap is edge-case behavior at the last wallpaper in the rotation.

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?

Zero parameters with 100% schema coverage, so nothing needs documenting. The description adds no parameter meaning because none exist, which meets the baseline for a no-arg tool.

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 verb ('switch to the next') and resource ('wallpaper'), plus the scope constraint 'in the current theme rotation', which separates it from set_wallpaper and prev_wallpaper without opening any schema.

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?

No guidance on when to use this over alternatives such as set_wallpaper, next_theme, or list_theme_wallpapers. The 'current theme rotation' phrase hints at the rotation context, but nothing states when-not or references a sibling tool.

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