horizon_torn_getKeyLog

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 only states 'Get current key log history', implying a read operation, but lacks details on authentication, caching, pagination, or any side effects. This is insufficient for an agent to 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 clear sentence, which is efficient and easy to parse. However, it could be slightly more informative without becoming verbose, so it does not achieve a perfect score.

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 complexity (5 parameters, no output schema), the description lacks essential context. It does not explain what the key log history contains, how results are ordered, the effect of parameters like 'limit' and 'offset', or the structure of the response. This leaves significant gaps for an agent.

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 covers 60% of parameters with descriptions, including 'key', 'comment', and 'timestamp'. The description adds no additional meaning beyond the schema. At this coverage level, the description should complement the schema, but it does not, resulting in a baseline score.

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 the verb 'Get' and the resource 'current key log history', indicating retrieval of key log data. However, it does not differentiate from sibling tools like 'horizon_torn_getKeyInfo' or 'horizon_torn_getKeyGeneric', which could cause confusion. The phrase 'current' adds some specificity about recency, but scope isn't fully defined.

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, nor does it mention exclusions or prerequisites. With many sibling tools, this omission makes it harder for agents to choose correctly.

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