horizon_torn_getMyForumPosts

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

No annotations provided; description does not disclose behavioral traits such as pagination, rate limits, sorting behavior, or return format. The input schema hints at timestamps and sorting, but the description 'Get your posts' conveys nothing about the tool's behavior beyond a basic read action.

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?

Extremely concise at three words, with no unnecessary information. However, the conciseness sacrifices helpful detail; a few more words could clarify scope without damaging conciseness, so it is not a perfect 5.

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 8 parameters, no output schema, no annotations, and exists among many similar forum-related siblings, the description is insufficient. It does not explain what 'posts' includes, how to use parameters like from/to, or what the response looks like, leaving the agent underinformed.

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 88% (7 of 8 parameters have descriptions), so the schema already explains parameter semantics. The description adds no additional meaning beyond what the schema provides, meeting baseline expectation but not improving it.

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 states verb 'Get' and resource 'your posts', clearly indicating it retrieves posts belonging to the user. However, among many forum-related sibling tools (e.g., getMyForumThreads, getUserForumPosts, getForumThreadPosts), the description does not differentiate what specifically 'your posts' includes compared to those, leading to 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 explicit guidance on when to use this tool versus alternatives like getMyForumThreads or getUserForumPosts. Does not mention prerequisites (e.g., authentication) or context such as retrieving only the current user's posts, which is likely but not stated.

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