horizon_torn_getWarfare

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

No annotations and no behavioral traits disclosed. The description does not indicate whether the tool is read-only, requires authentication, or provides historical vs. live data.

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?

Three words is too brief. While concise, it lacks sufficient information to be useful. Every word should earn its place, but here they do not provide clarity.

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 8 parameters, no output schema, and no annotations, the description is grossly incomplete. The agent cannot determine what data will be returned or how to properly invoke the tool.

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?

Description does not add any meaning to the parameters. Schema coverage is 75%, but the single required parameter 'cat' has no schema description and the description offers no hints. The description adds zero value beyond the schema.

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?

Description 'Get faction warfare' is vague. It doesn't specify what aspect of faction warfare (e.g., current wars, history, stats) is retrieved. Siblings like horizon_torn_getFactionWars and horizon_torn_getFactionRankedWarsHistory are more specific, but this description fails to distinguish itself.

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. The description does not mention context or prerequisites, leaving the agent to guess.

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