horizon_torn_getTornGeneric

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

No annotations exist. Description only states 'Get', implying read-only, but provides no details on error handling, pagination, rate limits, or data format. The tool's behavior beyond fetching is completely opaque.

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 (one phrase) but lacks any structuring of information. It does not effectively front-load key details, making it insufficiently informative.

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 13 parameters, no output schema, and no annotations, the description fails to provide necessary context. It does not explain parameter dependencies, expected input, or return value nature, leaving the agent underinformed.

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 85%, with most parameters having descriptions. However, the tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 any Torn selection' is vague. 'Torn selection' is undefined, and the tool's purpose is not clearly differentiated from numerous sibling tools like horizon_torn_getTornItems or horizon_torn_getTornCrimes.

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 generic tool vs. specific siblings. With many similar tools, lack of usage context makes selection difficult for an AI agent.

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