horizon_torn_getMyFactionCompletedChains

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

No annotations are provided. The description does not disclose behavioral traits such as side effects, rate limits, authentication requirements, or data freshness. For a read operation, it minimally implies no modification, but this is implicit.

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. It is appropriately concise with no wasted words.

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 simplicity of the tool (no output schema, few parameters), the description is minimal. It does not explain what a 'completed chain' entails, how the list is sorted by default, or how it differs from related tools like horizon_torn_getMyFactionChain. The context is insufficient for an agent to fully understand the behavior.

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 high (86%), so the baseline is 3. However, the description adds no meaning beyond the schema; it does not explain how parameters like 'to', 'from', 'sort', 'limit' relate to filtering completed chains. Thus, no added value.

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 action ('Get a list') and the resource ('your faction's completed chains'). It uses a specific verb and resource, and the 'my' prefix distinguishes it from sibling tools like 'horizon_torn_getFactionCompletedChains'.

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 is provided on when to use this tool vs alternatives. The description does not mention prerequisites, when-not-to-use, or distinguish it from similar tools like horizon_torn_getMyFactionChain or horizon_torn_getFactionCompletedChains.

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