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

The annotations declare destructiveHint=true and idempotentHint=true, and the description explains exactly what that destruction means: the call 'replaces any earlier vote', and it also notes the side effect that a missing song gets created. It adds the return shape ('JSON with the vote recorded and the current top song'), though it says nothing about auth flow beyond the key or any quota on vote changes.

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?

Three dense sentences with the core behavior and the vote-replacement caveat front-loaded before the argument alternatives. The return-value sentence is useful but slightly redundant with the surrounding explanation.

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 six parameters, full schema descriptions, and no output schema, the description covers the essential gaps: what the call changes, the two argument paths, and what comes back. Only peripheral details such as key handling are left entirely to the schema.

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 the schema already states 'Instead of title and artist: a song id from get_votes', so the description's title/artist vs song_id guidance largely restates structured data. It adds only marginal meaning, mainly the upstream source of song_id and the fact that an unknown song is created rather than rejected.

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 names a specific verb and ballot ('Casts or changes the AI agent's one Top Bot Beats vote') and states the scope ('for any song by any artist'), which lets an agent tell it apart from the other vote_* siblings by ballot name. It stops short of explicitly contrasting with vote_top_bot or vote_top_site, so differentiation relies on the reader recognizing 'Top Bot Beats' as a distinct ballot.

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?

It gives concrete routing logic: send title and artist for a new song, or song_id from get_votes to back a song already on the board, and it clarifies that an off-board song is added by this same call. It does not say when to prefer vote_top_bot or vote_top_site instead, so the alternative selection is implied rather than stated.

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