spotify_get_track_id

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

No annotations are provided, so the description must disclose behavior. It states the tool returns an ID as text but does not mention prerequisites (e.g., must have an active playback) or error states. The behavior is simple but lacks full disclosure.

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?

The description is two sentences with no redundant information. It front-loads the core purpose and specifies the return type efficiently.

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 description specifies the return value (ID as text) but lacks output schema. While the tool is simple, mentioning potential limitations (e.g., no ongoing playback returns null) would improve completeness. Still, it is adequate for a straightforward retrieval tool.

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?

The tool has no parameters, so the input schema is fully covered (100%). The description adds no parameter information, which is acceptable given zero parameters. Baseline 4 is appropriate.

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 clearly states the tool returns only the Spotify ID of the currently playing track, using the verb 'Get' and specifying 'ONLY the Spotify ID'. It distinguishes from sibling tools like spotify_get_track_uri and spotify_get_track_info by emphasizing the narrow scope.

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 implies usage when only the track ID is needed but does not explicitly state when to use this tool versus alternatives (e.g., spotify_get_track_uri for URI, spotify_get_track_info for full details). No when-not guidance is provided.

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