Lineupify status

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered by structured data. The description still adds real behavioral context beyond that: it clarifies this is an aggregate diagnostic that reports connection state, pending logins, and cache size, which tells the agent what kind of read to expect. It omits any note on cost or rate limits but none are implied for a local status read.

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?

Two sentences, front-loaded with the imperative 'Call this first' so the ordering guidance lands immediately, followed by the enumerated contents. Every clause earns its place, though the final clause about a waiting browser login is a slightly verbose restatement of the pending-login idea.

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?

With no output schema, the description carries the burden of describing return contents, and it does so by enumerating the reported fields. A read-only, zero-parameter diagnostic is adequately covered, though it could say more about what the agent should do with 'setup needed' beyond the adjacent setup 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?

Zero parameters, so the baseline of 4 applies and there is no parameter surface for the description to explain.

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 (shows) and enumerates concrete resources it reports: Spotify connection and identity, setup need plus exact steps, default options, in-progress drafts, cache size, and pending browser logins. This is more specific than a generic status tool, though it does not explicitly contrast itself against the sibling 'setup' tool it partially overlaps with.

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?

'Call this first' gives a clear ordering directive that tells the agent when to reach for this tool relative to all 21 siblings, and it hints that 'setup' is the follow-on when setup is needed. It stops short of stating exclusions or naming the alternative tool explicitly, so it is strong context but not full when/when-not guidance.

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