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

No annotations are provided, so the description carries the full burden. It only states the ordering (most recent first) but does not disclose authentication needs, rate limits, pagination, or whether it is a read-only operation. The minimal description adds little beyond the tool name.

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?

The description is extremely short, but it is under-specified rather than concise. It is a fragment lacking essential verb and context, which reduces its utility.

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?

Given three parameters and no output schema, the description is severely incomplete. It does not explain the return format, the effect of parameters like 'limit' or 'include_related', or any corner cases. The tool cannot be reliably used based on this description alone.

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?

The input schema has three parameters (song, limit, include_related) with 0% schema description coverage. The description provides no information about these parameters, their meanings, or constraints. This forces the agent to guess or rely on the schema defaults.

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 'Every time a song has been played (most recent first)' indicates it returns play history for a song, but it is a noun phrase rather than a clear verb-based statement. It distinguishes from sibling tools like 'song_stats' or 'get_setlist' but lacks specificity on the format (list, count, etc.).

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 usage guidance is provided. There is no mention of when to use this tool versus alternatives like 'song_stats' or 'search_shows', nor any prerequisites or limitations.

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