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

Annotations already declare readOnlyHint=true, and the description's REST path 'GET /v1/ledger/{id}/balance' is consistent with that safe-read profile. With the safety bar already covered by annotations, the description adds only the endpoint and restates the parameter behavior, disclosing nothing extra about return shape, pagination, or error behavior.

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?

One compact sentence plus an endpoint reference; the scope constraint is front-loaded and nothing is padded. The raw REST path is mildly redundant with the tool name for an agent caller, which keeps it from a 5.

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?

There is no output schema, so the description carries some burden for describing the return value (a balance figure, and how it differs when 'from' is supplied), which it only gestures at. For a simple read with fully documented inputs the definition is adequate but not complete.

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 the important 'from' semantics (difference vs. actual balance). The description's 'optionally per cost center and for a period (from/to)' merely mirrors that, meeting the baseline without adding format or default details beyond 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?

States a specific verb+resource ('the balance of one ledger') and quantifies scope ('one ledger', optional cost center and from/to period), which implicitly separates it from the sibling list_ledger_balances. It never names that sibling explicitly, so it stops short of full differentiation.

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 'the balance of one ledger' implies the single-ledger use case versus the batch list_ledger_balances, and the optional cost center/period modifiers hint at the supported modes. However, no explicit when-to-use or when-not-to-use guidance and no prerequisites are given.

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