playlist_track_count

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

With no annotations and no additional description, the tool's behavior is entirely undisclosed. It does not state the return format, scoping (e.g., current playlist or all playlists), or edge cases such as empty playlists.

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 words is under-specification rather than useful conciseness. While a trivial getter can be short, this phrase lacks any structuring, such as a sentence clarifying what is counted or returned.

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 tool with no output schema and no annotations, the description should at least explain the return value and scope. "Playlist track count" skips over whether this applies to the active playlist, whether it counts tracks or clips, and how results are represented.

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 zero parameters, so per the rubric the baseline is 4. There is no parameter documentation burden, and the description adds no parameter meaning because none exists.

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 "Playlist track count" is a near-verbatim restatement of the tool name, with no verb or agent-oriented framing. It does not clarify whether this returns the number of tracks in the playlist, the total number of clips, or something else.

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 guidance is provided about when to use this tool versus related siblings like playlist_track_info, playlist_all_tracks, or playlist_list_clips. The absence of any comparative or contextual direction leaves selection to inference.

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