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

Goes well beyond the readOnly/openWorld annotations by disclosing what the data actually represents, which sources feed it, which do not, and critically that entries hold request text only with no structured track/artist fields. That last point materially changes how an agent must parse results.

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 dense sentences, front-loaded with the core action and ordering before the scope caveats. Slightly long, but every clause (channel coverage, exclusions, entry shape) carries useful information rather than padding.

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 compensates by describing what entries contain and the absence of structured fields. Combined with the exhaustive channel coverage/exclusion list, an agent has everything needed to call and interpret this 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?

Schema description coverage is 100%, and the schema fully documents days, limit, and include_failed with defaults and maxima. The description adds no additional parameter semantics, 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?

States a specific verb+resource (list recent requests made to ZoneFoundry) with ordering ('newest first') and scope. It is clearly distinguishable from siblings like now_playing (current state) and search_music (catalog lookup).

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?

Gives substantial when-to-use context by enumerating the channels that DO produce entries (assistant, app voice/command, messaging bots, this connection) and explicitly excluding browsing-started playback. It does not name a sibling alternative for adjacent needs (e.g. now_playing), so it stops short of a 5.

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