horizon_torn_getTornCalendar

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

With no annotations, the description carries full behavioral disclosure burden. It only says 'Get calendar information', implying a read operation, but does not confirm safety, authentication needs, rate limits, or any side effects. The agent cannot assess risks.

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 short (4 words), which is concise but at the cost of informativeness. It does not earn its place by providing sufficient context. A sentence or two with more detail would be more effective.

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?

The tool has 3 parameters, all optional, but no guidance on typical usage or return values. There is no output schema, and the description does not explain what 'calendar information' includes (events, dates, times?). The description is incomplete for effective invocation.

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 documentation coverage is 100% for the three parameters, so the baseline is 3. The description adds no additional semantic context beyond what the schema already provides (e.g., what 'key', 'comment', 'timestamp' mean in the context of calendar data). No extra value.

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 a clear verb+resource combination ('Get calendar information'), but is too vague. It does not specify which calendar (global Torn calendar vs user-specific) or differentiate from sibling tools like horizon_torn_getMyCalendarTime. The purpose is implied but lacks specificity.

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 usage guidelines are provided. There is no indication of when to use this tool vs alternatives, nor any context about prerequisites or exclusions. The agent receives no decision support.

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