horizon_torn_getTornOrganizedCrimes

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

No annotations are provided, and the description only states 'information' without disclosing behaviors like authentication requirements, caching, rate limits, or what the response contains. 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 sentence of 4 words, which is concise but lacks structure and fails to provide essential details. It is minimally adequate but not more.

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 of the domain and the abundance of sibling tools, the description is incomplete. It does not specify the scope (global vs. personal vs. faction), the return format, or how it differs from other organized crime tools. The lack of an output schema further exacerbates this.

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, so each parameter is already documented in the schema. The description adds no additional meaning, resulting in a baseline score of 3.

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 'Get organized crimes information' provides a verb and resource but is too generic. It does not differentiate from sibling tools like horizon_torn_getMyFactionOrganizedCrimes or horizon_torn_getTornCrimes, leaving ambiguity about which organized crimes are returned.

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. There is no mention of prerequisites, context, or exclusions, making it difficult for an agent to decide among the many related organized crime tools.

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