Get a TIDAL user

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two useful behavioral facts: the default (no ID = current user) and a constraint (only public users are retrievable), but says nothing about failure modes for invalid/private IDs.

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 efficient sentence that front-loads both the resource and the two access modes. Nothing is redundant, though it could squeeze in slightly more guidance without bloat.

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?

An output schema exists, so return values need not be described. Given the tool is a simple single-param getter, the description covers the essential default and constraint, leaving only minor edge cases (invalid/private ID behavior) unaddressed.

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% and the schema itself only declares user_id as an optional integer/null. The description compensates by explaining the numeric ID type and the default behavior when it is omitted, but adds no format or range detail beyond that.

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 uses a clear verb+resource ("Return... user") and specifies the scope: the current user or another public user identified by numeric ID. It clearly distinguishes user lookup from the many other tidal_get_* siblings, though it doesn't explicitly contrast with the close sibling tidal_get_user_image.

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?

Usage is implied rather than stated: omitting the ID returns the current user, while supplying an ID fetches a public user. There is no explicit when-to-use/when-not guidance or mention of alternatives, but for a simple getter the intent is reasonably inferable.

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