horizon_torn_getMyFactionOrganizedCrimes

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

No annotations provided, so description carries full burden. Only states basic purpose, omitting behavioral details like authentication requirements, rate limits, pagination behavior, or data freshness. Minimal transparency for a 10-parameter tool.

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?

Extremely short (one sentence), but under-specification rather than conciseness. Lacks essential detail for a complex tool with 10 parameters and many siblings.

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?

Inadequate for a 10-parameter tool with no output schema and no annotations. Fails to describe return format, pagination, or filtering semantics. Sibling overlap (plural vs singular) increases risk of misuse.

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 80% (8 of 10 parameters have descriptions in schema). The description adds no additional parameter meaning beyond what schema already provides. Baseline 3 appropriate per guidelines.

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 states clear verb-resource: 'Get your faction's organized crimes'. However, there is no differentiation from sibling tools like horizon_torn_getMyFactionOrganizedCrime (singular) or horizon_torn_getMyAvailableOrganizedCrimes, which could cause confusion.

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. Lacks context about prerequisites, filtering, or scenarios where different sibling tools would be more appropriate.

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