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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds nothing beyond that—no note on pagination, filtering behavior, or what 'mappings' resolve to—so it contributes almost no 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?

The opening sentence is literally duplicated, wasting the most prominent position, and the remaining content is a machine-generated operation ID. There is no front-loaded statement of intent to justify the length.

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 no output schema, 0% parameter coverage, and nested-object parameters, the description needs to explain return shape and query/params usage. Instead it provides only a redirect to describe_operation, leaving an agent without enough to invoke the tool 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% and the two parameters (query, params) are undocumented in both schema and description. The only hint is that describe_operation holds the native request schemas, which offloads rather than explains parameter meaning.

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 merely repeats the HTTP path 'GET /api/account-mappings' twice plus an operation ID; it never states in plain terms what account mappings are or what the call returns. It is essentially a restatement of the title/name rather than an explanation of purpose.

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 only guidance is a pointer to describe_operation for native request schemas, which is a delegation of schema discovery rather than when-to-use guidance. It does not distinguish this tool from close siblings like get_account_mappings_by_id, get_account_mappings_effective, or get_account_mappings_summary_types.

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