tm1_list_dimensions

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. It only restates the operation and gives no information about output shape, pagination, permissions, or whether control dimensions are included. The read-only nature is inferable from 'list', but no deeper 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 extremely short and front-loaded, but it is under-specified rather than appropriately concise. The two words merely restate the tool name and omit essential context.

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 no output schema, no annotations, and an undocumented boolean parameter, the description is too sparse to fully guide selection and invocation. It does not clarify whether this returns all dimensions on the server or supports filtering, nor how includeControl should be set.

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 only parameter, includeControl, is not mentioned or explained in the description, and schema description coverage is 0%. The property name suggests its meaning, but the description contributes nothing beyond the input 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 uses a specific verb and resource, 'List dimensions', and is immediately understandable as an enumeration action. However, it does not distinguish this tool from sibling tm1_get_cube_dimensions, which also lists dimensions within a cube.

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?

No guidance is given on when to call this tool versus alternatives like tm1_get_cube_dimensions, tm1_list_cubes, or tm1_list_views. There are no exclusion criteria or context signals to help an agent choose this tool over its siblings.

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