get_karma_breakdown

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

The readOnlyHint annotation already covers the safety profile, and the description adds the grouping and ordering behavior ('per subreddit, highest first'). It does not, however, disclose whether the account parameter selects another user or defaults to the current one, which is a meaningful behavioral gap.

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?

Seven words convey the resource, grouping, and ordering with no filler or repetition. The description is front-loaded and every word earns its place.

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?

The tool is simple and has an output schema plus readOnlyHint, so the description does not need to explain return values or safety. The main missing piece is the account parameter's semantics, which makes the definition incomplete for confident invocation in all cases.

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%, so the description needed to clarify the optional 'account' parameter, but it never mentions it. The parameter name hints at its meaning, but the description does not state whether it takes a username/ID or what null means, leaving the agent to guess.

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 specific resource ('karma earned per subreddit') and the sort order ('highest first'), so an agent can tell what the tool returns. It does not explicitly contrast it with sibling tools like get_account_stats, but the resource is specific enough to avoid real confusion.

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 phrasing implies this should be used when a per-subreddit karma ranking is needed, but it provides no explicit when-to-use guidance or exclusions. There are no alternatives named, so an agent is left to infer context from the tool name and description.

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