horizon_torn_getPropertyTimestamp

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

With no annotations, the description must disclose behavioral traits. It only states 'Get current server time', failing to mention that this is a read-only operation, what the response contains, or any side effects. It does not clarify whether the 'timestamp' parameter changes the behavior (e.g., returning historical time).

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 a single phrase, which is concise but under-specified. It sacrifices completeness for brevity, leaving out essential context about the tool's use and parameters. It does not earn its place without adding value beyond the name.

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 three parameters and no output schema, the description is severely incomplete. It does not explain the role of 'timestamp' in retrieving server time, nor does it provide any usage context. The agent cannot infer proper invocation from this description alone.

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 100%, so baseline is 3. The description adds no additional meaning to the parameters; it doesn't explain how 'key', 'comment', or 'timestamp' are used in the context of getting server time. The 'timestamp' parameter's purpose (bypass cache or specific point in time) is left to the schema.

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 states 'Get current server time', which is a verb and a resource, but it's too generic. Among many sibling timestamp tools (e.g., getCompanyTimestamp, getFactionTimestamp), this description does not distinguish the property-specific context implied by the tool name. The purpose is clear in a vacuum but vague relative to 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 guidelines are provided about when to use this tool vs alternatives. There is no mention of context, prerequisites, or exclusions. The agent receives no help deciding between this and other timestamp tools.

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