spotify_get_time_remaining_formatted

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

The description discloses the output format and that it returns formatted text, but does not cover edge cases (e.g., when no track is playing) or any behavioral traits beyond the basic functionality. Since no annotations are provided, the description carries full burden and is adequate but not thorough.

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 extraneous text. Each sentence contributes useful information: what it does, output format, and use case. Front-loaded with the core action.

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 simple tool with no parameters and no output schema, the description covers the main purpose, output format, and ideal use case. It lacks explicit handling of edge cases (e.g., no current track), but given low complexity, it is reasonably 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?

With zero parameters, the schema coverage is 100% trivially. The description adds value by explaining the output format and usage context, which compensates for the lack of parameters. Baseline is 4 per rule for 0 parameters.

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 it gets the time remaining in formatted format, specifying the output format (M:SS or H:MM:SS) and use case (HUD countdown displays). The word 'ONLY' distinguishes it from sibling tools like spotify_get_time_remaining_ms.

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 provides clear context and suggests use for HUD displays, but does not explicitly mention alternatives or when not to use this tool. Sibling tools like spotify_get_time_remaining_ms are not referenced.

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