horizon_torn_getMyForumThreads

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

With no annotations, the description must fully disclose behavior. It only states 'Get your threads', implying a read operation, but fails to mention any side effects, authentication requirements, rate limits, or return format. The behavioral traits are not transparent beyond the obvious.

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 sentence with only three words. While concise, it lacks essential information, making it under-specified. It does not earn its place as it fails to provide value beyond the tool 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 7 parameters and numerous sibling tools, the description is severely incomplete. It does not explain the output, the effect of optional parameters like 'from' and 'to' for time filtering, or how this tool differs from related forum tools. No output schema exists to compensate.

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 86%, meaning most parameters have descriptions in the schema. The description 'Get your threads' adds no additional meaning to parameters like 'from', 'to', 'sort', or 'limit'. It does not clarify how these parameters affect the retrieval, but the schema already provides adequate 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 your threads' clearly states the action (get) and resource (your threads), indicating it retrieves the user's own forum threads. However, it does not differentiate from sibling tools like horizon_torn_getForumThreads or horizon_torn_getMyForumSubscribedThreads, leaving ambiguity.

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 versus alternatives such as horizon_torn_getForumThreads (which may retrieve all threads) or horizon_torn_getMyForumPosts. The description gives no context on preferred scenarios or exclusions.

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