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

Annotations already declare readOnly=false, openWorld=true, and idempotent=false. The description adds meaningful behavior beyond those annotations: the operation returns requestIds to track, the line number must be read first, and selectable values must come from list tools. It does not cover reversibility or side effects, but the annotations lower the burden and the added context is valuable.

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 a single front-loaded sentence with actionable instructions and no filler. It is efficient, though it packs three workflow instructions into one long semicolon chain, which slightly reduces scannability.

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 mutating, request-oriented tool with 7 parameters and no output schema, the description covers the key workflow: prerequisites (read the line number first), value sourcing (use matching list tools), and post-call behavior (track requestIds). It leaves permissions and exact return details unstated, but the schema and annotations carry much of that responsibility.

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 the baseline is 3. The description maps the operation to ledger account, counterparty, and reporting-group fields, but it does not materially add beyond the schema, which already documents each parameter and even explains special values like null to unset and [] to clear.

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 ('Change') and names the exact resource and fields: the ledger account, counterparty, or reporting-group assignments on one accounting transaction's debit or credit line. It clearly narrows scope to a single line, but it does not explicitly differentiate itself from sibling tools such as update_transaction or reprocess_transaction, so it just misses full sibling distinction.

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 gives an explicit call sequence: read the line number first, look up selectable values with the matching list tools, and track returned requestIds. This is useful context for correct invocation, but it does not state when not to use this tool or when an alternative such as update_transaction would be preferable.

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