horizon_torn_getMyForumFeed

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. However, it only states 'Get updates' without indicating read-only nature, authentication requirements, rate limits, or any side effects. This is insufficient for a tool that likely requires API keys and has specific behavioral traits.

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 concise with a single sentence. While it avoids fluff, it is too minimal and omits useful information. The structure is front-loaded but the brevity costs clarity. A score of 4 reflects that it is concise but could be more informative without being verbose.

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 complexity of the tool (a user-specific forum feed) and the lack of an output schema, the description is incomplete. It does not explain what data is returned (e.g., list of updates, structure), nor does it address common usage patterns or requirements. The schema and annotations are minimal, so the description should compensate but fails to do so.

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?

The input schema has 100% coverage for all parameters (key, comment, timestamp) with descriptions in the schema. The tool description adds no additional meaning beyond the schema, meeting the baseline expectation for parameter semantics.

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 your threads and posts' clearly identifies the verb and resource, indicating that this tool retrieves updates related to the user's forum threads and posts. However, it lacks specificity on what constitutes an 'update', and given the many sibling tools like horizon_torn_getMyForumFriendsUpdates and horizon_torn_getMyForumPosts, it does not clearly differentiate from them.

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?

The description provides no guidance on when to use this tool versus alternatives. There are sibling tools for specific forum feeds (e.g., horizon_torn_getMyForumFriendsUpdates for friend updates, horizon_torn_getMyForumPosts for posts), but the description does not state that this tool should be used for a combined feed or general activity. No exclusions or context are given.

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