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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds scope and output context by specifying that it ranks all family members by points, badges, and streaks and returns a ranked list, which is valuable since no output schema is provided.

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 three short, front-loaded sentences with no filler: what it gets, what it shows, and what it returns. Every sentence 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?

For a zero-parameter, read-only getter, the description covers the object, scope, content, and return shape despite the lack of an output schema. It is complete enough, though it could be stronger by explicitly distinguishing itself from nearby gamification or leaderboard siblings.

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?

There are no parameters, so the schema fully covers the argument surface. The description reinforces that the call takes no options and always produces a family-wide ranking, which exceeds the baseline for a zero-parameter tool.

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 verb and resource: 'Get the family gamification leaderboard,' then details the content ('rankings by total points, badges earned, and streaks') and scope ('all members of your family group'). This is enough to distinguish it from individual gamification and summary tools in the sibling list.

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 description makes clear that this tool is for a family-wide leaderboard, so an agent can infer when to call it. However, it gives no explicit when-to-use guidance and does not contrast itself with overlapping sibling tools such as get_gamification_summary, get_points_and_level, or list_badges.

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