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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned field set, which is genuinely useful, but says nothing about pagination limits, empty results, or result size behavior beyond what the schema states.

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?

A single compact sentence with the key scoping detail (per-administration, per-date) front-loaded; the trailing 'Accounting.GLAccountBalance.' type reference is slightly cryptic filler but costs little.

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 list tool with a fully documented 4-parameter schema and no output schema, the description covers scope, date semantics and return fields adequately. Only cross-tool routing (vs. transactions/scheme tools) is left 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 100%, so all four parameters are already documented in the schema, including date pattern, limit bounds and the next_offset pagination hint. The description only restates the date format, adding no semantics 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+resource: returns balances of every GL account for an administration on a given date, and even enumerates the returned fields (account code, description, amount). It implicitly separates itself from yuki_list_gl_account_transactions (balances vs. individual postings) but never names that sibling, so it stops short of a 5.

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 'on a date' scoping implies the tool is for point-in-time balance snapshots, but there is no explicit when-to-use/when-not, no mention of the alternative transaction-listing tool, and no stated prerequisite such as resolving administration_id via yuki_list_administrations.

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