horizon_torn_getMyFactionNews

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

No annotations are provided, so the description carries the full burden. It does not disclose behavioral traits such as whether it's read-only, required authentication, rate limits, or how the 'cat' parameter affects results. The minimal description fails to compensate for missing annotations.

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 of 5 words, which is concise but not necessarily effective. It sacrifices informative value for brevity. While not verbose, it is underspecified for a tool with 9 parameters.

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 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the return format, pagination, or how parameters like 'to', 'from', 'sort', and 'limit' filter results. The agent lacks enough information to use the tool correctly.

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 89%, so the input schema already describes most parameters adequately. The description adds no additional meaning beyond 'news details'. The 'cat' parameter is required but not explained in the description, though the schema documents it as 'News category type'.

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 clearly states the tool retrieves 'your faction's news details', specifying the resource (faction news) and the action (get). It is distinct from sibling tools like horizon_torn_getMyFactionBasicInformation or horizon_torn_getMyFactionMembers, as it specifically focuses on news.

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. It does not mention prerequisites, context, or when not to use it. Among many faction-related sibling tools, the agent receives no hints for selection.

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