get_handlebars_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 behavioral disclosure. It describes the return shape in detail with a concrete example, which is helpful, but it does not mention potential errors, permissions, or confirm that the operation is read-only (though implied by 'Get'). This is adequate but not exhaustive.

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 well-structured with Args, Returns, and Example sections, making it easy to scan. The example is somewhat lengthy but provides valuable concrete detail, so every part earns its place.

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), the description is complete: it states the purpose, describes the parameter, explains the return value, and gives an example. The presence of an output schema further reduces the need to describe return structure, but the description does so anyway, making it self-sufficient.

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 no descriptions for its single parameter, so the description compensates by explaining 'table_name: Name of the table to get variables for' and providing a concrete example ('Image'). This adds clear meaning beyond the schema.

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 opens with 'Get all available template variables for a table,' using a specific verb ('Get') and a clear resource ('template variables for a table'). It elaborates that it returns columns, foreign keys, and special variables, and distinguishes it from sibling tools by focusing on template variables rather than setters or other getters.

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?

The description clearly indicates when to use this tool: when you need template variables for a table to use in Handlebars templates. It provides context about the use case (row_markdown_pattern, markdown_pattern) and gives an example, but it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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