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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context: results are scoped to 'this account' and ordered 'newest first', which is beyond the annotations, but it does not mention response format, pagination, or account authentication requirements.

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, compact sentence that fronts the key information (achievements, account scope, ordering). Every word earns its place, and there is no filler or repetition.

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 tool with annotations covering safety, the description is nearly complete: it states what is returned and the order. It lacks explicit notes on output schema or edge cases (e.g., no badges), but the low complexity makes this a minor gap rather than a blocking issue.

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 0 parameters and the schema description coverage is 100%, so the description is not required to explain parameter meanings. Per the baseline for 0 parameters, this dimension deserves a 4; the description adds no unnecessary parameter detail.

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 clearly identifies the resource (badges/achievements) and the scope (this account), plus the sort order (newest first). It avoids tautology and is easily distinguishable from siblings like get_rank and get_stats, though it lacks an explicit imperative verb.

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?

Usage is implied rather than stated: the description implies you use it to retrieve the current account's achievements, but it gives no explicit guidance about when to prefer it over alternatives or any exclusions. There are no close sibling tools competing for the same purpose, reducing the need for explicit routing.

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