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. The description adds useful domain context by saying it reads from saved settings and chart data and does not push a bill, but it does not explain the returned precedence structure or any caveats beyond the safety profile already in annotations.

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 description is two tight sentences with the core read operation front-loaded and the non-action constraint immediately following. Every sentence earns its place.

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 read-only preview tool with no output schema, the description gives enough to understand the overall purpose but not enough to know the return shape of the account precedence. Combined with the low parameter schema coverage, an agent has only a partial picture of how to interpret the result.

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%, so the description must compensate for the undocumented input object. It mentions 'one destination,' which loosely maps to provider, but it does not explain the provider enum values, the invoice_id UUID requirement, or how the nested input is structured.

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 states a specific read operation and resource: existing invoice/client/workspace account precedence for one destination, drawn from saved settings and chart data. The phrase 'Does not push a bill' helps distinguish it from mutation siblings such as set_invoice_posting_account, though it does not explicitly name the alternative.

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 description implies this is a read-only inspection preview before posting or changing an invoice posting account, but it never states exactly when to use it versus preview_set_invoice_posting_account or set_invoice_posting_account. Usage is inferable from the read-only framing but not explicitly guided.

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