horizon_torn_getFactionLookup

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

No behavioral traits are described. No annotations exist. The only mention is about authentication, which does not disclose behavior such as read-only or mutating effects.

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 short but under-specified rather than concise. It lacks essential information, making it unhelpful.

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 large number of sibling faction tools and no output schema, the description is completely inadequate. It fails to provide any meaningful context for the agent.

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 100% and parameters are well-documented in the schema. However, the description adds no value and includes a misleading statement that a public access key is 'required,' while the schema indicates it is optional if passed via header. This could confuse the agent.

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 'Requires public access key' does not state what the tool does. It provides a precondition but not the purpose. The name hints at faction lookup, but the description lacks a verb or resource.

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 guidance on when to use this tool versus alternatives. Many faction-related siblings exist, but the description offers no context for choosing this one.

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