horizon_torn_getForumTimestamp

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

No annotations. Description does not disclose caching behavior, rate limits, authentication requirements, or return format. For a simple tool, this is insufficient to understand its safety and operational characteristics.

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?

One sentence, no fluff. Efficient but may be too terse. Still, it earns its place.

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?

No output schema. Description does not explain the purpose of the 'timestamp' parameter or clarify that this is forum-specific. Among many similar tools, this is incomplete for an agent to select correctly.

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%, so parameter descriptions are already provided. The tool description adds no additional meaning beyond the schema, meeting baseline expectation.

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?

Description 'Get current server time' is clear in verb and resource, but lacks specificity among many sibling timestamp tools (e.g., getCompanyTimestamp, getTornTimestamp). The tool name includes 'Forum', but description omits this context, making it hard to distinguish.

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 other timestamp tools. No exclusions, prerequisites, or context provided. Agent must infer usage from name alone.

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