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

No annotations, so the description carries the full burden and does well: it discloses idempotency, the no-op/skipped behavior when the GL chart isn't configured for native settlement, the exact double-entry posting rules per match state, and that the matcher still owns reconciliation_status. The only gap is it doesn't state auth/permission requirements or what the response payload looks like.

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?

Front-loads the core action, then enumerates the branch-specific postings compactly. The doc reference is a useful pointer but slightly lengthens it; overall still tight.

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 single-param mutation tool with no annotations and no output schema, the description covers behavior, side effects, and idempotency well. It leaves parameter identity underspecified and doesn't mention permissions, but the core semantics are 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 0% and parameter count is 1, but the description says nothing about what entry_id refers to (a bank entry ID from which system) or its format. Baseline for 1 param with no description is weak; the description does not compensate.

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 (Post ... bank entry into the GL) plus a parenthetical scope qualifier (clean-bank settlement). This clearly distinguishes it from siblings like post_gl_journal_entry or reverse_gl_journal_entry.

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 description explains the conditions that select each posting variant (matched vs unmatched vs previously-suspensed) and notes the no-op case, which effectively tells the agent when the tool will vs won't do anything. It doesn't name an alternative tool explicitly, but the conditions are clear.

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