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

Annotations already declare readOnly=true, idempotent=true, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that — deterministic per-date output, UTC basis, and seasonal gating — but says nothing about rate limits, failure modes, or what happens for out-of-season or future dates.

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?

Front-loaded with the core action and the enumerated kinds, followed by constraints and the return shape. The single dense paragraph is efficient, though the parenthetical about ideas.slopped.site is slightly buried and could be trimmed or split for scanability.

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 two-optional-parameter read tool with no output schema, the description covers it all: what is picked, the determinism and timezone rule, seasonal availability, when to use it, and the return fields (id, name, link, a line about it). An agent has everything needed to call it correctly and interpret the result.

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% and both parameters already carry descriptions including the enum meanings, so the schema does the heavy lifting. The description echoes the kind list and adds a little color about the 'idea' kind (machine-made prompts from ideas.slopped.site, to make or vote on), but adds no syntax or format detail beyond the schema. 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?

Uses a specific verb ('Pick') plus a concrete resource ('the slopped.site thing of the day') and enumerates the possible kinds: artwork, game, codex entry, clock, song, SK8 level, or twelve ideas. It's immediately clear this is a single daily selection rather than a lookup or search, though it never names which sibling (get_artwork, get_codex_entry) to use instead for a specific known item.

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?

Explicitly states 'Use when someone wants one recommendation or a daily pick,' which sets a clear usage condition and implicitly excludes targeted lookups. It also gives the seasonal constraint (seasonal pieces only in their season) and the determinism rule (same pick for everyone on a given date, UTC), but stops short of naming alternatives for when a user wants a specific item by id.

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