get_user_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but it does not state whether the profile is public, whether authentication is needed, how errors are returned, or what the response contains.

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 concise and front-loaded, but it errs on the side of under-specification. It uses one sentence with no filler, yet it omits the input parameter and any usage context that would make the brevity effective.

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 there is no output schema and no annotations, a single sentence of description is inadequate. The description does not clarify the role of the username parameter, the public nature of the data, or the expected response shape, leaving important gaps for a tool with one lookup parameter.

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?

The schema shows one username parameter with 0% description coverage, and the description never mentions it. The agent is left to infer that username is the required identifier and that it is string input with length at least 1; nothing clarifies that it is required for the call despite being marked optional.

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 states a clear operation and resource: retrieving a Discogs user profile. However, it does not differentiate this from sibling tools like discogs_identity or edit_user_profile, leaving some ambiguity about whether this returns public profiles or the authenticated user's own profile.

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 usage context is provided. The description gives no indication of when to prefer get_user_profile over discogs_identity or edit_user_profile, nor any mention of prerequisites such as authentication or username requirements.

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