Get the user image

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is known. The description adds 'authenticated user's' and 'URL' as context, but says nothing about how the optional dimensions parameter affects behavior, caching, or authentication requirements beyond the implicit authenticated scope.

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 wasted words. It states the action and return value directly.

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 simple read-only image getter with an output schema and safety annotations, the description is nearly complete. The only gap is the absence of any mention of the optional dimensions parameter, but its name and schema constraints make its purpose reasonably inferable.

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% for the single 'dimensions' parameter, and the description does not mention it at all. With one undocumented parameter, the description fails to compensate for the schema's lack of parameter semantics.

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, resource, and scope: 'Return the authenticated user's profile-image URL.' This clearly distinguishes it from sibling image tools such as tidal_get_album_image, tidal_get_artist_image, and tidal_get_playlist_image, which target different resources.

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?

The resource is specific enough that usage is implied: call it when you need the authenticated user's profile image. However, there is no explicit when-to-use guidance, no exclusions, and no routing among the many sibling image-fetch tools, so the agent must infer the context.

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