horizon_torn_getMarketPropertiesRental

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states 'Get properties rental listings' without mentioning caching, pagination, rate limits, auth requirements, or return format. This is a significant gap.

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 very concise at 4 words. While not verbose, it lacks substance and fails to earn its place beyond restating the tool name. It could include more detail without losing conciseness.

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 7 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the rental listings contain, how to interpret results, or any operational nuances. The tool is part of a large set of siblings, but no contextual clues are provided.

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 71% (5 of 7 parameters have descriptions), which is moderate but not high enough to relieve the description of adding value. The description adds no parameter information beyond what is in the schema. Two parameters (limit, offset) are undocumented in the schema and description.

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 rental listings' clearly identifies the action (get) and resource (properties rental listings). It is specific to rental listings, distinguishing it from general property tools like horizon_torn_getMarketProperties, but it does not explicitly differentiate from siblings.

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 like horizon_torn_getMarketProperties or horizon_torn_getMarketBazaar. No context about prerequisites or exclusions.

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