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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing truncation behavior — lists may be truncated and counts accompany them so large ledgers don't flood context — which an agent needs to interpret results correctly.

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?

Two tightly written sentences: the contents come first, the truncation/counts caveat second. No filler and nothing is buried.

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 an output schema present and annotations covering the safety profile, the description covers what is needed to call and interpret the tool. The only shortfall is the absence of routing guidance relative to sibling read tools, which is minor for a discovery call.

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 100%, including the ledger default behavior and the payeeLimit default of 50, so the schema does the heavy lifting. The description adds only indirect context ('truncated lists') and no format or syntax details beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Read a ledger's working vocabulary') and then enumerates exactly what comes back: attributes, open accounts, currencies, payees, years, source files. That enumeration clearly separates it from siblings like listLedgerEntries or getEntryContext, which target individual entries rather than the ledger's vocabulary.

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 phrase 'in one call' implies this is the broad discovery/orientation tool, but the description never says when to prefer it over getEntryContext or listLedgerEntries, nor does it state any prerequisites. Usage is inferable but not explicit.

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