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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: one entry per reaction and most-recent-first ordering, which tells the agent the shape and sort of the result.

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 dense sentence that front-loads the core question and then the sourcing detail. It is efficient with no filler, though the run-on structure with parenthetical asides makes it slightly harder to parse at a glance.

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?

With no output schema, the description should carry more of the return shape; it says one entry per reaction, most recent first, but never indicates what an entry contains (e.g. who gave it, when). For a simple two-parameter read tool this is adequate but leaves a gap an agent would want filled.

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 coverage is 100%, so the baseline would be 3, but the description goes further by tying subject_id to its real sources (kudos_subject from the feed, round id from list_rounds) and clarifying that live_round is the self-player case. That meaning is not fully captured by the schema alone.

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 and question: who gave kudos to a round, badge or crown, and it names the two source paths (a friend's kudos_subject from get_hole19_feed, or the player's own live_round id from list_rounds). That is enough to distinguish it from generic round tools, though the verb is phrased as a question rather than an explicit 'list kudos givers'.

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?

It gives concrete guidance on how to source the required inputs (kudos_subject from the friends' feed, round id from list_rounds), which is genuinely useful. It does not, however, say when to prefer this over alternatives or what happens for the other subject_kind values such as achievement, crown or party_group.

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