horizon_torn_getMyCrimes

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

With no annotations, the description must disclose behavioral traits. It fails to indicate that the tool requires a crimeId (implying it is for a specific crime), whether it is read-only, or any side effects. The description is too brief to be useful for safe invocation.

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 extremely concise but at the expense of clarity. At only six words, it fails to convey the tool's specific purpose, parameters, or relationship to siblings. It is underspecified rather than appropriately concise.

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 having 4 parameters, no output schema, and numerous sibling tools, this description is severely incomplete. It does not explain the return format, differentiate from similar crime-related tools, or provide enough context for an AI agent to choose and invoke the tool correctly.

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?

Although schema descriptions are provided for all parameters (100% coverage), they are minimal (e.g., 'Crime id') and the tool description adds no additional meaning. The description does not explain the role of required parameter 'crimeId' or how optional parameters like 'timestamp' affect behavior.

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 your crime statistics' is vague and does not specify what kind of crime statistics are returned. The tool name and required parameter 'crimeId' suggest it retrieves details for a specific crime, but this is not communicated in the description. Sibling tools like 'getMyAvailableOrganizedCrimes' and 'getMyOrganizedCrime' overlap without differentiation.

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 versus alternatives. For example, if a user wants a list of available organized crimes, they would need to know to use 'getMyAvailableOrganizedCrimes' instead. The description omits any context about prerequisites or typical use cases.

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