horizon_torn_getMyForumSubscribedThreads

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

With no annotations, the description should disclose behavioral traits like side effects, idempotency, or auth needs. It only says 'get updates', which is insufficient. No mention of rate limits, caching, or return format.

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 concise sentence, but it lacks structure. For a simple tool, this might be acceptable, but it could be more descriptive. No front-loading of critical info.

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. The tool has 3 optional params and low complexity, but the description does not explain what 'updates' means (e.g., thread metadata, new posts count). Incomplete for an AI to confidently invoke.

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% (3 params documented). The description adds no extra meaning beyond what the schema provides for key, comment, timestamp. Baseline 3 is appropriate.

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 updates on threads you subscribed to' specifies the resource (subscribed threads) and action (get updates). It distinguishes from siblings like getMyForumThreads (all threads) and getMyForumFeed, but 'updates' is vague (new posts, activity?). Score 3 because it's clear 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 guidance on when to use this tool vs. alternatives such as horizon_torn_getMyForumFeed or horizon_torn_getMyForumFriendsUpdates. No exclusions or prerequisites mentioned.

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