horizon_torn_getMarketGeneric

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

The description does not disclose any behavioral traits such as whether the operation is read-only, idempotent, or has side effects. With no annotations provided, the description fails to compensate, leaving the agent without critical safety information.

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 (4 words) but lacks structure and substantive content. Conciseness is beneficial only when the description remains informative; here it is under-specified and fails to guide the agent.

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 tool has 11 parameters, no output schema, and many sibling tools, the description is woefully incomplete. It provides no information about return values, filtering logic, or how to effectively use the parameters. This is inadequate for an AI agent.

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 82%, so the parameters are mostly documented in the schema itself. The description adds no additional meaning beyond the parameter names and brief schema descriptions. It meets the baseline but does not enhance understanding.

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 any Market selection' is vague and does not specify what a 'Market selection' refers to. It fails to differentiate from sibling tools like horizon_torn_getMarketAuctionHouse or horizon_torn_getMarketBazaar, which have more specific purposes. The purpose is unclear.

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 the many other market-related sibling tools. There is no mention of prerequisites, context, or alternatives. The description offers no decision support.

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