tm1_list_subsets

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not mention output format, whether private and public subsets are included, or how the optional hierarchyName affects behavior. Minimal behavioral context is provided.

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 efficient sentence with no wasted words. It is front-loaded and readable, though its brevity contributes to the lack of completeness in other dimensions.

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?

For a tool with two parameters and no annotations or output schema, the description is too thin. It names the primary resource and dimension, but leaves the optional hierarchy parameter and result behavior unexplained. An agent could make basic assumptions but would lack critical context for correct invocation in edge cases.

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?

Schema description coverage is 0%, and the description only implicitly maps to dimensionName via 'of a dimension.' The optional hierarchyName parameter is completely unexplained, including whether it filters results to a specific hierarchy. The description adds little meaning beyond the parameter names themselves.

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 states a specific verb and resource: 'List subsets of a dimension.' It is immediately distinguishable from sibling tools that list views, cubes, dimensions, processes, or elements. However, it does not clarify scope (e.g., all subsets, public/private, or subsets for a specific hierarchy), which keeps it from being fully precise.

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 about when to use this tool versus alternatives such as tm1_list_hierarchies or tm1_list_dimension_elements. No context is provided for when listing subsets is appropriate or how it differs from related list operations.

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