Spotify Session Status

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

With no annotations, the description carries the full burden, and it does disclose that the tool inspects cookie origin and validity — meaningful behavioral context beyond the name. It stops short of saying whether this is strictly read-only, whether it exposes credential material, or how it behaves when no session exists.

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?

A single front-loaded sentence with no filler, and the diagnostic target is stated before the detail. It is arguably compressed to the point of using jargon ('where the cookies come from') that an agent must interpret.

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?

An output schema exists, so return values need not be explained, and zero parameters means no input complexity. Still, for an unannotated diagnostic tool, the description omits failure modes and the login precondition, which are the main things an agent needs to interpret the result.

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 takes zero parameters and the schema is empty, so there is nothing for the description to clarify. Baseline 4 applies; no parameter information is missing.

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 verb 'Diagnose' and resource 'session' are specific, and the description clarifies the diagnostic focus is cookie provenance and validity, which separates it from a plain status read. It does not, however, name or contrast with the sibling 'spotify_status', so an agent must infer the boundary between the two.

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?

There is no explicit statement of when to call this versus 'spotify_status', 'spotify_login', or 'spotify_logout', and no prerequisites such as needing prior login. The troubleshooting intent is only implied by the word 'Diagnose'.

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