tm_list_variables_sets

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

Discloses that only metadata is returned and raw CSV content is excluded, which is important behavioral context. No annotations exist, so description provides necessary transparency. Could mention read-only nature explicitly but implied.

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?

Front-loaded with main action. Two paragraphs without wasteful content. Could be slightly tighter but still efficient.

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, no annotations, and the description covers purpose, usage guidelines, behavioral details, and output content, it is complete for a list tool. Output schema exists but description already lists returned fields.

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?

No parameters in schema (0 params, 100% coverage), so baseline 4 is appropriate. Description adds no param info but none needed; it focuses on the tool's purpose and output.

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?

Clear verb and resource: 'List all variables sets owned by the authenticated user.' The description explicitly distinguishes from sibling tools like tm_get_variables_set by noting the scope difference.

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 explicit use case: answering 'what variables sets do I have available to attach to a profile?' during load test setup. Also clarifies when not to use (for CSV content) and directs to tm_get_variables_set for full metadata.

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