horizon_torn_getMyMedals

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention authentication requirements, rate limits, or what happens if no medals are achieved. The description is too minimal to inform an AI agent about the tool's behavior.

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, very concise sentence. It is front-loaded and efficient, but could include additional context without becoming verbose. Still, it is not wasteful.

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 and only three optional parameters, the description is too brief. It does not explain what the response contains, whether results are paginated, or any filtering capabilities. For a tool that retrieves 'achieved medals', more context is needed.

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 description coverage is 100%, so the description adds no value beyond the schema. The description does not mention or explain the parameters (key, comment, timestamp). Baseline score of 3 is appropriate as the schema already documents them.

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 your achieved medals' uses a specific verb ('Get') and resource ('achieved medals') clearly indicating the tool retrieves the user's own medals. This distinguishes it from sibling tools like 'horizon_torn_getTornMedals' which likely retrieves all medals.

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 on when to use this tool versus alternatives like 'horizon_torn_getMyHonors' or 'horizon_torn_getTornMedals'. There is no mention of prerequisites, context, or when not to use it.

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