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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered structurally. The description adds nothing beyond that - no return shape, no pagination, no filtering behavior, no note about what the mapping resource represents.

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?

Short, but the first two sentences are the identical URL string repeated verbatim - pure duplication with zero information gain. Front-loading is absent because there is no substantive content to front-load.

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 and 0% parameter coverage mean the description must carry the burden, and it does not: no purpose, no parameters, no behaviors. The single pointer to describe_operation and execute_read-adjacent siblings is the only useful fragment.

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 both parameters ('query' as an arbitrary property bag and empty 'params') are undocumented. The description does not compensate at all; it only points at describe_operation for the real request schema, which is a pointer rather than semantics.

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 restates the tool name as a raw URL path ('GET /api/accounting/account-mappings') twice. It implies a listing of account mappings but does not describe what a mapping is, what it contains, or how it differs from near-identical siblings such as get_account_mappings_5900b624a5f0d38407bcecf4, get_account_mappings_by_id_..., or get_account_mappings_effective_....

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 tool versus the many account-mapping siblings in the same namespace. The only guidance is the note that describe_operation provides native request schemas, which hints at how to discover parameters but says nothing about tool selection.

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