merit_list_dimensions

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

With no annotations present, the description carries the safety burden. It uses a read-only verb ('List') and a get-style endpoint, and it discloses that setting allValues includes inactive/ended values. It does not mention authentication, rate limits, or output shape, but for a simple read-only enumeration this is reasonably transparent.

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 concise sentences: the first front-loads the purpose and endpoint, the second explains the only parameter behavior. There is no redundant or filler wording.

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 one-parameter list operation with no output schema, the description says what is returned (dimensions and their values), how to include inactive/ended values, and the endpoint. It does not state the default value of allValues or pagination behavior, but those are minor gaps for this simple tool.

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 input schema already describes allValues at 100% coverage, so the baseline is 3. The description adds meaningful semantics by explaining that 'all values' specifically means including inactive/ended values, which goes beyond the schema's generic 'Include all dimension values'.

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 the action ('List'), the resource ('Merit Aktiva dimensions and their values'), and the exact endpoint (POST /api/v2/getdimensions). None of the many sibling list tools target dimensions, so the tool is unambiguous.

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 intended use is plain: retrieve Merit Aktiva dimensions and their values. The allValues note adds the one conditional behavior. It does not explicitly name alternatives or when-not conditions, but there is no overlapping sibling tool, so this is clear context without exclusions.

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