get_current_user

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

The description discloses that the tool returns the user's profile with id, name, country, and other unspecified fields ('etc.'). However, it does not mention behavioral traits like authentication requirements, error conditions (e.g., no user signed in), or any side effects. Given the lack of annotations, the description carries the full burden but provides only partial transparency.

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?

The description is a single, clear sentence that directly states the tool's function and examples of returned data. It contains no unnecessary words or filler, making it highly concise and well-structured.

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?

Given the tool's simplicity, the description provides enough information for basic understanding but lacks details like authentication requirements, potential errors, or a full list of return fields (it ends with 'etc.'). With no output schema, the description should be more complete to cover these gaps.

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?

With zero parameters, the input schema is fully covered by the description (100% coverage trivially). The description does not need to add parameter details, and the baseline for 0-parameter tools is 4, which is appropriate here.

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 clearly states the tool retrieves the profile of the signed-in Spotify user, listing example fields like id, name, and country. It uses a specific verb ('Get') and resource ('profile'), and it distinguishes itself from sibling tools like get_currently_playing or get_playlist, which have different purposes.

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 explicit guidance on when to use this tool versus alternatives is provided. The purpose is implied by the name and description, but there is no mention of exclusion or alternatives, such as using authenticate or auth_status for authentication-related tasks.

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