tm_get_variables_set

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

Discloses return fields and omission of raw CSV. With no annotations, the description effectively communicates the tool's behavior as read-only and structured. Doesn't mention error handling but acceptable for a simple get operation.

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?

Two sentences, each informative. No redundancy. Front-loaded with purpose, then details. Highly concise.

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 one required parameter, no output schema, and no annotations, the description adequately covers purpose, return shape, and limitation (no raw CSV). Lacks error or existence info but sufficient for a simple fetch.

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 single parameter variables_set_id is not described beyond the schema. With 0% schema coverage, the description adds no meaning; even a brief clarification would improve scoring.

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 'Get a single variables set's metadata' with a specific verb and resource. It distinguishes from sibling tools like tm_list_variables_sets by focusing on a single item and referencing the return shape.

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?

Provides context by comparing return shape to tm_list_variables_sets and advises using the in-app UI for raw CSV inspection, implying when not to use this tool. Could explicitly state alternative use cases but sufficient for guidance.

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