horizon_torn_getMarketProperties

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

With no annotations provided, the description must disclose behavioral traits. It only states the basic purpose, omitting details like rate limits, authentication requirements, or data scope. This is insufficient for a tool with 7 parameters and no output schema.

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 single-sentence description is concise but under-specified. It front-loads the purpose but lacks necessary detail to be truly helpful.

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 high number of parameters (7), no output schema, and many sibling tools, the description is incomplete. It does not explain the response format or how this tool fits into the broader market domain.

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 71%, so the schema already explains most parameters. The description adds no extra meaning beyond the purpose. It does not clarify the semantics of parameters like 'limit' or 'offset' that lack schema descriptions.

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 properties market listings' specifies a verb and resource, but it is ambiguous among sibling tools like 'horizon_torn_getMarketPropertiesRental' and 'horizon_torn_getMarketBazaar'. It does not clarify what distinguishes this endpoint from other property market tools.

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 alternatives such as 'horizon_torn_getMarketPropertiesRental'. The description lacks context for selecting this endpoint among many market-related siblings.

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