Save Spotify client ID

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

Annotations already declare this is a non-destructive, idempotent write. The description adds real behavioral context beyond that: the required redirect URI must be exactly http://127.0.0.1:8765/callback, and redirectPort=0 resets to 8765, implying persistence and overwrite semantics. It doesn't say where the value is persisted or what the response looks like, but the added constraints are substantive.

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?

Front-loads the primary action and the critical constraint (client ID format, exact redirect URI) before moving to the optional parameters. Dense but every clause carries information; only the parenthetical redirect-URI detail slightly interrupts the flow.

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 3-parameter, no-output-schema setup tool with annotations covering the safety profile, the description supplies the format constraints, the exact redirect URI requirement, and the port-reset behavior an agent needs. It stops short of describing persistence location or any auth requirement, but nothing essential for correct invocation is missing.

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?

Schema description coverage is 0%, so the description carries the full burden, and it does: clientId is defined by format and source (32 hex chars, dashboard app page), lastfmApiKey is scoped to a second ranking source, and redirectPort is explained as only-needed-when-different with a 0-resets-to-8765 special case. All three parameters gain meaning not present in the schema.

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?

States a specific verb and resource ('Save the Spotify client ID') and adds concrete detail about the value (32 hex chars from the developer dashboard). It does not explicitly distinguish itself from siblings like status or connect, but 'setup' is unambiguous enough for an agent to identify it.

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?

It gives the motivation ('so it is not needed in the MCP config') and conditions for the optional params ('for a second ranking source', 'only if the user registered a different port'), which implies when to use them. However there is no explicit guidance on when to call setup versus status/connect/disconnect, leaving the workflow ordering to inference.

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