Get template variables

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the purpose (getting dynamic variables) but does not mention that this is a read-only operation, whether it requires any permissions, or what the response format looks like. No behavioral traits are disclosed beyond the action itself.

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 short sentence with no superfluous words, making it concise and front-loaded. It is appropriately sized for the simplicity of the tool, though the brevity limits its informativeness.

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 tool's simplicity (one parameter, no output schema), the minimal description is barely adequate. However, it omits any details about the return value structure, whether the template must already exist, or any preconditions. For an agent to call it correctly, more context would be helpful, especially given the large sibling toolset.

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 0% description coverage, and the description does not explain the 'templateId' parameter at all. The tool name and description do not hint at what kind of identifier is expected (e.g., a GUID, a numeric ID) or how it relates to templates. The description adds no value beyond the schema definition.

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 clearly states the verb 'Get' and the resource 'dynamic variables of a template', making the tool's purpose transparent. However, it does not explicitly differentiate from sibling tools like gambot_get_template, relying on the tool name rather than description to set it apart.

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, such as whether it should be called before sending a template to obtain required variables, or if it overlaps with gambot_get_template. The description provides no context or exclusions.

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