horizon_torn_getFactionGeneric

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

No annotations are provided, and the description offers no behavioral context—such as read/write nature, rate limits, or output format. The agent learns nothing beyond the minimal 'get' verb.

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, but it is too brief to be useful. True conciseness would include essential context without verbosity.

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?

With 15 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to explain the response structure, valid selection values, or how to combine parameters effectively.

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 80% parameter description coverage, so the schema already clarifies parameter meanings. The tool description adds no additional semantics or guidance on how parameters interact.

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 any Faction selection' is vague. It identifies the verb and resource but does not specify what constitutes a 'selection' or how it differs from sibling tools like 'horizon_torn_getFactionMembers' or 'horizon_torn_getFactionBasicInformation'.

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 the many faction-specific sibling tools. An agent cannot determine if this generic tool is for custom queries not covered by specialized tools.

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