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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered. The description adds genuinely useful behavioral context about feed composition (followed DJs, scanned posts, imports), but says nothing about ordering guarantees beyond 'newest' or pagination behavior.

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?

One sentence, front-loaded with the verb and resource, then the qualifying detail about feed composition. No filler, no repetition of the title.

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 annotations carrying the safety profile and no output schema to explain, the description's main job is defining what the feed is, and it does so clearly. The only gap is the undocumented 'limit' parameter, which is minor for a single optional integer.

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?

There is a single optional 'limit' parameter with 0% schema description coverage, so neither schema nor description documents it. The description's 'newest tracks' implies recency ordering, which is the only semantic hint offered; the meaning and bounds of 'limit' (1-50) are left entirely to the schema.

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 ('Get') and resource ('the newest tracks in this account's CrateWire feed') and enumerates the three sources that compose the feed (followed DJs, scanned posts, imports). This makes it distinguishable from siblings like get_dj_recent_tracks and get_radar, though it never names them explicitly.

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?

The description explains what the feed contains but gives no when-to-use guidance: nothing says to prefer this over get_dj_recent_tracks, get_radar, or find_known_tracks, and no prerequisites or exclusions are stated. Usage must be inferred from the tool name alone.

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