get_credits

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

No annotations provided, so description carries the burden. It discloses the authentication requirement (SPOTIFY_SP_DC), which adds behavioral context beyond the schema. However, it does not mention error handling, rate limits, or what happens without the credential.

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?

One concise sentence that front-loads the purpose and appends the key requirement. No wasted words.

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?

Has an output schema but doesn't need to describe returns. However, the parameter is undocumented, and the tool's complexity (1 param, no annotations) is not fully addressed. The description omits what 'value' should be, making it incomplete for correct usage.

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 coverage is 0%, and description does not explain the single required parameter 'value' (likely a track ID or URL). Despite low coverage, description adds no parameter meaning, which severely impacts agent ability to invoke correctly.

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?

Clearly states the verb 'Fetch' and the resource 'a track's credits', listing examples (performers, writers, producers). This distinguishes it from sibling tools like get_track or get_lyrics.

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?

Explicitly notes the prerequisite '(needs SPOTIFY_SP_DC)', indicating a required credential. While it doesn't mention when-not-to-use or alternatives, the context of sibling tools implies it's for specific credit data needing special auth.

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