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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds worthwhile domain context (it mutates displayed manual holdings only, not brokerage records) but says nothing about the concurrency guard, idempotency key behavior, or what happens on a mismatch — the behaviors an agent most needs before calling a destructive mutation.

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?

Three tight sentences, front-loaded with the action and scope, then the consequence, then the guardrail. No filler and nothing repeated from the title.

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?

An output schema and rich annotations relieve the description of return-value and safety disclosure, and the synced/imported exclusion is valuable. However, for a destructive, idempotent mutation with three undocumented parameters, omitting the expected-value precondition leaves the agent without enough to invoke it correctly on the first try.

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 there are 6 parameters, so the description must carry the load. It covers only transaction_id, quantity, and price; the non-obvious expected_quantity / expected_price_per_share preconditions and the operation_id idempotency key are left entirely unexplained.

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 precise verb and resource: 'Adjust quantity and entry price of one exact manually recorded BUY transaction by its ID.' It also scopes the target ('manually recorded', 'not a brokerage trade'), which implicitly separates it from record/remove siblings. It stops short of naming a sibling tool as the alternative for synced/imported rows.

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?

Gives an explicit negative condition — 'synced and imported transactions cannot be changed' — plus a procedural prerequisite, 'Check the user's prior record and confirm the intended correction.' That clearly tells the agent when it must not call the tool, though it does not route to the sibling to use instead.

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