get_earned_badges

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

There are no annotations, so the description carries full behavioral burden. It implies a read-only action through the verb 'Get', but discloses nothing about return format, authentication requirements, scope limitations, or whether any side effects exist. This is minimal information.

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 short sentence with no filler words. The verb and resource are front-loaded, making it easy to scan and parse.

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?

Despite having an output schema, the description lacks sufficient context around what 'earned badges' encompasses and how this differs from multiple badge-related siblings. With no annotations and no usage guidance, an agent may not correctly route between get_earned_badges and get_badge_challenges.

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 tool has zero parameters, which sets a baseline of 4. The description does not need to explain parameters, and the empty schema offers no conflicting details.

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 'Get earned badges for user' uses a specific verb and resource, clearly indicating a read operation that returns badges a user has earned. It is mostly distinct from siblings like get_available_badge_challenges or get_non_completed_badge_challenges, but does not explicitly name them or clarify the contrast.

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 guidance is provided on when to use this tool versus the badge-related sibling tools. The description neither names alternatives nor states conditions, leaving the agent to infer selection from the tool name alone.

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