bg3_template

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that resolution walks the ParentTemplateId chain; it says nothing about whether this is a pure read, whether unresolvable keys fail or return null, or what happens if the chain is broken.

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?

A single tight sentence with the verb and mechanism front-loaded and no filler. It is efficient, though arguably terse to the point of omitting needed detail.

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?

An output schema exists so return values need not be explained, but with two params at 0% schema coverage, no annotations, and a non-trivial inheritance-resolution behavior, the one-line description is insufficient for an agent to invoke this confidently.

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 description coverage is 0%, so the description must compensate. It usefully clarifies that 'key' accepts a MapKey GUID or Name, but the second parameter 'layers' is never mentioned at all, leaving half the interface semantically undocumented.

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 names a specific verb (Resolve), a specific resource (root template), and the mechanism (ParentTemplateId chain), plus the accepted key formats (MapKey GUID or Name). It is clear what the tool does, though it does not differentiate itself from potentially overlapping siblings such as bg3_get_entry or bg3_static.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer its place among ~40 sibling tools entirely on its own.

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