horizon_torn_getMyFactionBasicInformation

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

No annotations are present, so the description must disclose behavioral traits. It only states 'Get your faction's basic details', which implies a read operation but does not mention authentication requirements, rate limits, data scoping, or any potential side effects. The description is insufficient for transparency.

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 very concise (6 words), but it lacks necessary detail for a tool with many siblings. While it is front-loaded, it sacrifices completeness for brevity, which is a trade-off.

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 absence of an output schema and annotations, and the presence of numerous sibling tools, the description is too minimal. It does not explain what 'basic details' entail, how to interpret the output, or how this tool differs from similar ones like 'horizon_torn_getMyFactionMembers' or 'horizon_torn_getMyFactionStats'.

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 100% description coverage for its three optional parameters (key, comment, timestamp). The description adds no additional meaning beyond what the schema already provides, so it meets the baseline but does not enhance understanding.

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 uses a specific verb 'Get' and resource 'your faction's basic details', and the 'My' prefix clearly distinguishes it from other faction-related tools like 'horizon_torn_getFactionBasicInformation' or other user-oriented tools. However, it does not elaborate on what 'basic details' include, which could be vague.

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 is provided on when to use this tool versus its many siblings, such as other 'MyFaction' tools or general faction lookups. There is no mention of prerequisites, context, or when not to use it.

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