horizon_torn_getTornSubcrimes

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the action (Get) and resource (Subcrimes), omitting details like read-only nature, authentication requirements, rate limits, or any side effects. This is insufficient 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 (3 words) but fails to provide essential context. It is not front-loaded with critical information and lacks structure. While brevity is valued, this underspecification harms usability.

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 Torn API (many sibling tools) and absence of output schema, this description is critically incomplete. It does not explain what subcrimes are, their relation to other crime data, or expected return structure. An agent would struggle to use this tool correctly without external knowledge.

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% with each parameter having a description (e.g., crimeId, key, comment, timestamp). The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 says 'Get Subcrimes information', indicating the resource is 'Subcrimes'. However, within the context of Torn API with many crime-related siblings (getTornCrimes, getMyCrimes, getMyOrganizedCrime, etc.), it fails to clarify what Subcrimes are or how they differ. Sufficient for a basic understanding but lacks 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 usage guidelines are provided. The description does not specify when to use this tool over alternatives, nor does it indicate prerequisites or conditions. This forces the agent to infer usage solely from the name.

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