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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that the image payload is opt-in via include_image and mentions the wallpaper 'if any' and infinite-zoom Scroll, which hints at optional/conditional fields. It does not cover error behavior for a missing id, which is the main remaining behavioral gap.

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 resource and its returned fields, then the usage cue. Every clause carries information and there is no filler.

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?

With no output schema, the description usefully enumerates the return contents, including conditional items like the wallpaper and Scroll. Combined with annotations covering the safety profile, an agent has enough to invoke this correctly.

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 coverage is 100%, so both parameters are already documented, and the description's note that include_image returns 'the picture itself' largely restates the schema. The id parameter's format is left entirely to the schema's pattern and example. Baseline 3 applies when structured data carries the parameter detail.

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?

Names a specific verb and resource ('Get one Fresh slop piece by id') and enumerates the fields returned (title, category, subtitle, description, links, wallpaper, Scroll), so the agent knows exactly what it retrieves. It also names the two siblings it follows (search_artwork, of_the_day), distinguishing it from list/search 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?

States an explicit sequencing cue: 'Use after search_artwork or of_the_day,' which tells the agent when this is the right next call. It does not state exclusions (e.g., that it fails for unknown ids or that bulk retrieval needs a different tool), so it stops short of full when/when-not guidance.

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