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

Beyond the annotations (destructiveHint=true, idempotentHint=true), it discloses that removal is permanent and cascades across all transaction records for the holding, that certain holding source types are rejected, and that no trade or broker state is touched. It does not explain how expected_transaction_count interacts with safety or what happens on a mismatch.

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?

Four short sentences, front-loaded with the destructive action, then the confirmation protocol, then the blocked cases, then the scope disclaimer. Every sentence adds distinct decision-relevant information with no filler.

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?

The output schema relieves the description of explaining return values, and the destructive semantics are well covered. However, for a destructive tool with a mandatory count guard and operation_id, the absence of any parameter explanation leaves a real gap an agent could stumble on.

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?

With 5 parameters at 0% schema description coverage, the description carries the burden but only implicitly covers portfolio_name and ticker ('one holding in one portfolio'). Critical guard parameters — expected_transaction_count (an obvious optimistic-concurrency check) and confirm (const: true) — are never explained, leaving the agent to infer how to satisfy them.

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 gives a specific verb and resource with precise scope: 'Permanently remove all manual transaction records for one holding in one portfolio.' That scope (all records for one holding) is meaningfully distinct from the singular sibling remove_my_portfolio_transaction, though the description never names that alternative explicitly.

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?

It states clear preconditions ('Ask for explicit user confirmation and list the affected history first') and explicit exclusions ('Mixed-source, legacy, CSV and synced broker holdings are blocked'), which tells the agent when NOT to call. It stops short of naming the correct sibling for single-transaction removal.

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