get_playback_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only' and adds a cost indicator '🟢/🟡 (1-2 reads)', which are genuinely useful safety and cost signals. However, it omits edge-case behavior such as what happens when there is no active playback, a null context URI, or an unresolvable catalog item.

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 tight, front-loaded sentence with zero filler. The verb 'Resolve' leads, followed by the input source, output fields, and a compact cost/read-only tag. Every element earns its place and no information is repeated from the schema.

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?

The tool is low-complexity (one optional, fully documented parameter), and the description lists the main returned fields, which partially compensates for the missing output schema. Still, the description doesn't explain error behavior (e.g., no active playback context) or clarify how 'json' output is structured beyond what the schema's 'raw API object' phrase implies, so it is adequate but not complete.

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 100%: the single response_format parameter is fully documented in the schema with enum values and their meanings. The tool description adds nothing parameter-specific, but with full schema coverage the baseline of 3 applies and no compensation is needed.

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 ('Resolve'), a specific resource ('current playback context URI'), and the concrete outputs (playlist/album/artist/show name, owner, track count). It cites its data source (GET /me/player), which helps distinguish it from nearby siblings like get_playback_snapshot or get_currently_playing, though it doesn't explicitly contrast itself with them.

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 when-to-use or when-not-to-use guidance is provided, and no alternative tools are named. Given a large sibling set with overlapping playback tools (get_context_inspect, get_playback_snapshot, get_now_playing, get_currently_playing), an agent gets no explicit direction on when to pick this tool over those. Usage is only implied by the purpose statement.

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