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 discloses irreversibility ('Permanently delete'), the non-obvious side effect (transactions survive and their spending is reassigned to the next matching line or 'other'), the required permission level, and the return value. This is exactly the destructive-operation context an agent needs.

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 short sentences, zero filler, and the destructive nature is front-loaded before the side-effect and permission details. Every sentence earns its place.

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 destructive mutation with no output schema, the description covers permanence, cascade behavior, authorization, and the response shape ({ success: true }), leaving no gap an agent would need to guess at before calling.

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 both parameters (lineId, trackerId) are documented in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 for a fully-covered 2-parameter schema.

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 plus resource ('Permanently delete a line from a tracker'), which cleanly separates it from delete_tracker, delete_transaction and update_tracker_line in a crowded sibling list. An agent can identify the operation 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?

The description implies when it applies ('Permanently delete a line') and gives a precondition ('Requires manage access to the tracker'), but never names an alternative or a when-not condition (e.g. archive_tracker, remove_transactions_from_tracker, update_tracker_line). Usage is inferable but not routed.

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