Get template variables

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so no behavioral contradictions. However, the description adds no extra context beyond the tool name, such as whether variables are cached, how often they update, or what format they are returned in.

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 sentence of four words, extremely concise. It front-loads the verb 'Get', making the purpose immediately clear without any wasted words.

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 parameters and no output schema, the description could still benefit from explaining what 'global template variables' are or how they relate to other template operations. The current text is minimally sufficient but lacks context for an agent unfamiliar with the domain.

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 tool has zero parameters, and the schema coverage is 100%. With no parameters to describe, a baseline score of 4 is appropriate since the description adds no confusion.

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 'global template variables', directly indicating the tool's function. It distinguishes from sibling tools like 'arcane_template_get' and 'arcane_template_update_variables' by specifying 'global', implying system-wide scope rather than per-template.

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 alternatives such as 'arcane_template_get' or 'arcane_template_list'. The description does not mention prerequisites, exclusions, or context for when fetching global variables is appropriate.

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