Get dimension values

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are paged and optionally filtered, which is useful operational context, but says nothing about page-size limits, default ordering, or what an empty result means.

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?

A single front-loaded sentence with no filler; the core resource and its example values come first. It is efficient but arguably under-scaled for a 7-parameter tool, so terseness shades into sparseness.

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?

With 7 parameters, 3 of them required, zero schema descriptions, and no output schema, the definition leaves too much unexplained for an agent to call it confidently. Nothing tells the agent what organizationNumber must be, how paging should be sized, or what the filter fields actually match.

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% across 7 parameters, so the description carries the full burden and largely fails it. "Paged" loosely maps to pageIndex/pageSize and "optionally filtered" gestures at code/isDisabled/dimensionType, but organizationNumber, acceptLanguage, and the enum's four values get no explanation at all.

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?

States a specific verb and resource ("Returns dimension values") and grounds it with concrete examples (cost centers/projects), so an agent knows exactly what kind of data comes back. It stops short of distinguishing itself from the sibling get_dimension_settings, leaving the values-vs-settings boundary implicit.

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 statement of when to call this tool versus alternatives, no prerequisites (organizationNumber is required but its role is unexplained), and no mention of the closely related get_dimension_settings. "Optionally filtered" hints at a use case but gives no conditions for choosing this tool.

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