horizon_torn_getProperty

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

No annotations are provided, so the description must disclose behavioral traits. The description only states 'Get a specific property' without mentioning read-only nature, side effects, rate limits, or any other behavior. This is essentially a tautology, providing no transparency.

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 short (one sentence) but fails to add value. Being concise is good, but every sentence should earn its place; here, the sentence barely says more than the tool name. It is under-specified rather than appropriately concise.

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's complexity (4 parameters, many sibling tools, no output schema), the description is completely inadequate. It does not explain what a property is, how to differentiate from similar property tools, or what the return value looks like. The context provided is minimal and insufficient for correct usage.

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%, meaning all parameters are documented in the input schema. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate since the schema already handles parameter documentation.

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 a specific property' clearly indicates the action of retrieving a property resource. However, it does not distinguish from sibling tools like 'getPropertyGeneric' or 'getPropertyLookup', which may have similar purposes. The verb 'Get' and noun 'specific property' are specific enough to convey the basic function.

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?

There is no guidance on when to use this tool versus alternatives such as 'getPropertyGeneric' or 'getMyProperty'. No when-to-use, when-not-to-use, or exclusions are provided. The description is insufficient for an AI agent to decide between siblings.

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