tm1_list_hierarchies

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

There are no annotations, so the description carries the full behavioral disclosure burden. It only says 'List,' which implies read-only behavior, but it does not mention output format, pagination, ordering, error behavior, or anything beyond the action already captured by the tool name.

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, focused sentence with no filler, and the key action and target are front-loaded. Every word contributes to the meaning.

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?

This is a simple one-parameter listing tool, and the description gives enough to understand its basic purpose and required argument. However, without annotations or an output schema, it would benefit from a note on what is returned or any failure conditions.

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?

With one parameter and 0% schema description coverage, the description adds minimal semantic value by linking 'dimension' in the text to dimensionName. It does not explain the expected format, examples, or edge cases, but the single parameter is simple and largely self-explanatory.

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 uses a specific verb and resource: 'List hierarchies of a dimension.' It clearly states what the tool does and the target resource, though it does not explicitly differentiate itself from sibling listing tools.

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 phrase 'of a dimension' implies the tool is used when the caller needs hierarchies for a specific, named dimension. However, it does not state when to choose this tool over similar listing tools or provide any exclusions.

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