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

With no annotations, the description carries the full burden and does so well: it declares the operation permanent and irreversible, warns to confirm first, and discloses the non-obvious side effect that the holding and portfolio cash balance are recalculated. It omits auth/permission requirements and error behavior, so it falls short of a 5.

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 action and its consequence, then the irreversibility warning, then the ID source. No sentence is filler and each adds a distinct fact.

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 destructive tool with no annotations and no output schema, the description covers the essentials: permanence, side effects, and ID provenance. It is nearly complete, though it could note permission requirements or what happens to the linked portfolio/holding records.

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% and the single parameter is fully documented with a UUID pattern and source hint. The description's mention of obtaining transactionId from get_investment_transactions merely duplicates the schema, so it adds no meaning beyond structured data — baseline 3.

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 ('delete') and resource ('investment transaction'), and the qualifier 'investment' distinguishes it from the sibling delete_transaction. An agent can identify exactly what is being removed without opening the schema.

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 clear pre-call guidance ('confirm with the user before calling') and tells the agent where to obtain the ID ('from get_investment_transactions'). However, it never explicitly contrasts this with delete_transaction or states when an agent should prefer an alternative such as update_investment_transaction.

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