Settings: get postingaccounts

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

Annotations already declare readOnlyHint, idempotent, and non-destructive, and the description reinforces READ-ONLY and adds context beyond that: pagination support, the need to page until all rows are covered, and the absence of a delete endpoint. No contradiction with 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 informative and well-structured, with the READ-ONLY notice front-loaded. Though it includes some repetition of the tool name, every major section earns its place and it is not bloated.

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?

Given the output schema exists and all parameters are documented in the schema, the description provides enough context for correct invocation: purpose, use case, alternative tool, pagination behavior, and endpoint.

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 coverage is 100%, so the schema fully documents each parameter. The description adds practical meaning around `limit` and `offset` by explaining the large size of a chart and advising to page until `rows` is covered.

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 uses a specific verb and resource: 'Get all postingaccounts' and clarifies this is the chart of accounts. It explicitly distinguishes itself from `accounts_list` for bank accounts, so an agent can tell siblings apart.

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?

It gives a concrete use case: finding a posting account number before booking office supplies. It also names when to use a different tool (`accounts_list`) and explains pagination strategy because the full chart can run to several hundred rows.

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