horizon_torn_getTornFactionTree

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

Annotations are absent, so the description must fully convey behavioral traits. It only states 'Get full faction tree', with no mention of read-only nature, caching, response structure, or side effects. Minimal 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 short (4 words) but lacks necessary detail. It is not verbose, but conciseness should not sacrifice clarity. It earns a 3 as minimally adequate.

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 no output schema and no annotations, the description fails to provide enough context for an agent to understand the tool's behavior or output. 'Full faction tree' is ambiguous, and the tool's complexity is not addressed.

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?

All three parameters (key, comment, timestamp) have descriptions in the schema. The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 says 'Get full faction tree', which is a verb and resource but 'faction tree' is vague and not differentiated from sibling faction tools like 'getFactionBasicInformation' or 'getFactionMembers'. It lacks specificity on what the tree represents.

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. There are many sibling faction tools, but the description provides no context on when 'faction tree' is appropriate or how it differs from other faction queries.

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