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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds nothing on top — no mention of pagination, what a 'dimension' record contains, error behavior for a missing id, or scoping to the workspace. It does not contradict the annotations, but it contributes zero behavioral context.

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?

Very short, but the first sentence is duplicated verbatim, which is pure waste rather than concision. There is no front-loaded statement of purpose — the reader hits a URL path and a hex operation ID before any 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?

No output schema exists, a nested 'params' object is required, and 0% of parameters are documented anywhere — yet the description supplies none of the missing information about the response shape or the required identifier. For a nested-object lookup tool this leaves the agent unable to call it confidently.

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 two parameters: the required nested 'params.id' (a bare string with only length constraints) and the free-form 'query' object with additionalProperties. The description never mentions either; the ':id' placeholder in the URL is the only clue that it identifies a connection, and 'query' is entirely unexplained.

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 is literally the tool title repeated twice: a raw REST path 'GET /api/accounting-integration/connections/:id/dimensions' with no plain-language statement of what the operation returns. An agent can infer 'fetch dimensions for a connection' only by parsing the URL, and it cannot distinguish this from the many sibling get_accounting_integration_connections_* tools, which are also raw-path restatements.

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 statement of when to use this versus siblings such as get_accounting_financial_dimensions_by__ or the other connection sub-resource tools. The only actionable hint is the trailing note that 'describe_operation provides native request schemas', which at least points the agent at a prerequisite tool for schema detail, but no use/exclude conditions are given.

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