get_user_trophies

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

With no annotations, the description carries the behavioral burden. It clearly indicates a read-only retrieval operation and scopes it to the current user's data. It does not disclose auth requirements, failure behavior, or empty-result handling, but for a simple getter this is acceptable yet not rich.

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 front-loaded sentence with no filler. It efficiently states the action and the resource, earning its place entirely.

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?

The tool is a low-complexity getter with one auth parameter and an output schema, so return values do not need to be described. The phrase 'current user's' plus the access_token parameter gives enough context for an agent to invoke it, though explicit guidance on token provisioning would make it fully 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 description coverage is 0%, and the description does not mention the access_token parameter at all or explain how it is used. The parameter name is conventional and self-explanatory, which mitigates the issue, but the description does not compensate for the missing schema-level documentation.

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 uses a specific verb ('Get') and a clear resource ('current user's Reddit trophies and achievements'), making the tool's purpose immediately understandable. It also differentiates from siblings: no other tool in the sibling list targets trophies, so there is no ambiguity.

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 intended usage is implied: call this when you need the current user's Reddit trophies and achievements. However, there is no explicit guidance about when not to use it or which alternative tool to prefer, though the unambiguous naming makes this a minor gap.

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