Get ledger account

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

The annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds only the single-result qualifier and says nothing about not-found behavior, scoping, or response shape, which is acceptable but not rich.

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 one short, front-loaded sentence with no filler or structural waste. It could be slightly more informative without becoming bloated, but it is appropriately concise for a simple get operation.

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 simple read-only getter with two parameters and no output schema, the description is minimally viable. However, it does not mention how to discover valid ledger_account_ids, what happens when the ID is not found, or that list_ledger_accounts should be used for enumeration, leaving some operational context implicit.

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 only 50% because ledger_account_id has no schema-level description. The tool description does not explain the identifier's meaning or relationship to administration_id, so it fails to compensate for the low coverage. The administration_id parameter is already well-described in the schema.

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, 'Retrieve', and resource, 'a single ledger account', which clearly states what the tool does. The word 'single' distinguishes it from the sibling list_ledger_accounts tool.

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?

No guidance is given about when to use this tool versus list_ledger_accounts or other get_* tools. An agent must infer from the name that this is for fetching one known account, and no alternative or exclusion is mentioned.

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