horizon_torn_getTornCrimes

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

No annotations provided. The description adds no behavioral context beyond the implied read operation. Does not mention authentication requirements (key parameter optional), rate limits, or data freshness.

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 concise (3 words) but under-specified. Lacks necessary detail to be useful, crossing from conciseness into omission.

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 no output schema and many similar sibling tools, the description is incomplete. Does not clarify what 'crimes information' contains or how it differs from other crime-related tools.

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 coverage is 100%, so baseline is 3. Description adds no information about parameters beyond what the schema provides (key, comment, timestamp).

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 crimes information' is vague and fails to distinguish from many sibling tools like horizon_torn_getTornOrganizedCrimes, horizon_torn_getMyCrimes, etc. It essentially restates the tool name without adding specificity about which crimes (global, personal, faction) 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 siblings. Does not explain the scope (e.g., global Torn crimes vs user-specific crimes) or any prerequisites.

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