get_user_karma_breakdown

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

With no annotations provided, the description carries the full behavioral disclosure burden. 'Get' implies a read operation and 'by subreddit' hints at output granularity, but the description does not disclose authentication needs, whose karma is returned, or any API-specific behavior.

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 front-loaded sentence with no filler or redundancy. It is appropriately concise, though it lacks the structural richness that would make it stand out.

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-value details are covered elsewhere, but the description omits important context: whether access_token is required, whose karma is fetched, and how this tool relates to sibling Reddit getters. For a tool involving authenticated user data, this is a meaningful gap.

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 description adds nothing about the access_token parameter. The parameter name and title are self-explanatory, providing a floor, but the description itself contributes no semantic clarification about whether the token is required or how it is used.

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 identifies a specific verb ('Get') and a specific resource ('user's karma breakdown by subreddit'), making it distinct from the many sibling get_user_* tools. It does not explicitly contrast with a sibling, so it falls just short of a 5.

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?

There is no guidance about when to use this tool versus alternatives such as get_user_overview or get_user_comments. The purpose is implied by the name, but prerequisites and selection criteria are left entirely unstated.

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