get_user_unlocks

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

With readOnlyHint=true and openWorldHint=true already declared, the safety profile is covered, and the description usefully adds the 'newest first' ordering and the default 24h window. It still omits auth requirements, pagination behavior, and what happens when multiple time parameters are supplied.

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?

Two clipped sentences with zero filler, front-loading what the tool returns before the time-window constraints. It is dense and slightly telegraphic, but every clause carries information.

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 7-parameter read tool with no output schema, the description nails the time-window semantics but leaves limit/cap behavior (max 500), hardcore_only's meaning, and the user default unexplained. It is adequate but not complete.

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 only 57%, but the description adds genuinely non-schema information: the mutual exclusivity of minutes/from/date and the default 24h window, which the schema does not state. It says nothing about limit, hardcore_only, or user, so it only partially compensates for the coverage gap.

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 identifies the resource (a user's unlocks) and the ordering (newest first), so the agent knows it returns a reverse-chronological list. However, it is a bare noun phrase with no verb and never clarifies what an 'unlock' is, leaving it ambiguous against the sibling get_achievement_unlocks.

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?

'One of minutes, from[/to], date; default last 24h' constrains how to use the time parameters but says nothing about when this tool should be chosen over siblings such as get_achievement_unlocks or get_user_game_progress. No exclusion or alternative routing is given.

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