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

Annotations already declare readOnly, idempotent, openWorld=false and non-destructive, so the safety profile is fully covered. The description adds real context that annotations cannot: results are CrateWire-identified from posts (a derived corpus, not raw data) and are returned newest-first. It says nothing about pagination, the limit cap of 50, or behavior for unfollowed handles.

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 with no filler; the operation and ordering come first, the scope constraint second. Nothing is redundant.

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 does cover the shape of the result (recent tracks, newest first) and the eligible domain. It omits limit semantics and what happens when the handle is not a followed DJ, which an agent needs to call 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 description coverage is 0%, so the description bears the full burden, and it only partially compensates: 'a followed DJ's posts' implies handle refers to a followed DJ's identifier. The limit parameter (1-50) is never mentioned, so no default, cap, or pagination meaning is conveyed.

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?

Specific verb (get) plus resource (recent tracks) scoped to a followed DJ's posts, with the ordering ('newest first') stated. It is distinguishable from get_my_feed and get_set_tracklist by its 'followed DJ's posts' scope, though it never names those siblings to sharpen the boundary.

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?

'Works for DJs this account follows on CrateWire' is an implied precondition that rules out arbitrary handles, which is useful. However, it names no alternative for the cases it excludes (e.g., searching arbitrary tracks via find_known_tracks), leaving the routing decision to inference.

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