horizon_torn_getUserIcons

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

No annotations are provided, and the description only states 'Get icons information', implying a read operation. It does not disclose behavioral traits like authentication requirements (API key), caching behavior (timestamp parameter), or that the tool can accept both user ID and Discord ID. The description is insufficient to fully understand 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, concise sentence that directly states the tool's purpose. There is no extraneous information, and it is efficiently front-loaded.

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?

Given the absence of an output schema and the presence of 4 parameters, the description is too minimal. It does not explain what 'icons information' includes, nor does it help differentiate from numerous sibling tools with similar patterns. The tool lacks sufficient context for an agent to use it correctly.

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 input schema has 100% description coverage, with clear descriptions for each parameter (e.g., 'User id or user discord id', 'API key (Public)'). The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 states 'Get icons information for a specific player', identifying the action and target. However, it doesn't specify what 'icons' refers to (e.g., profile icons) or differentiate from the sibling getMyIcons, which also retrieves icons but for the current user.

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 description provides no guidance on when to use this tool versus alternatives like getMyIcons or other getUser* tools. It does not mention prerequisites, such as requiring an API key or that the 'id' can be a user ID or Discord ID.

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