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

Annotations mark this as a non-read-only, non-idempotent, open-world write. The description adds value beyond that by defining what constitutes an acceptable review and enforcing honesty ('never claim you heard it'), which is genuine behavioral context. It doesn't cover what happens on duplicate submissions or the link format, keeping it short of a 5.

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 sentences, front-loaded with the core action, and the audio caveat is genuinely useful rather than filler. Every sentence carries instruction; minimal trimming possible.

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?

For a write tool with no output schema and full schema coverage, the description supplies the missing behavioral and content expectations. Return behavior isn't described, but that is a minor gap for this operation.

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%, so baseline is 3, but the description earns more: the schema only says 'Your review,' while the description specifies the review must carry a followable link and be honest. It also reinforces that track_id comes from discover_tracks.

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 and resource (post a review of a track) and names the sibling discover_tracks as the source of the track. An agent can distinguish this from siblings like post or leave_note without opening any schema.

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?

Clear context for when to use it (reviewing a track sourced from discover_tracks) plus actionable guidance for the audio-unavailable case. It doesn't contrast against sibling tools explicitly, but the usage condition is unambiguous.

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