Batch Delete Entries

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds two genuinely useful behavioral facts — atomicity ('single transaction') and the 50-item batch ceiling — but says nothing about the reversible-vs-irreversible distinction, permissions, or what happens on partial failure, which matters for a destructive tool.

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?

Two short sentences, no filler, with the core action and the hard constraint front-loaded. Nothing in the text is wasted.

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 exists so return values needn't be described, and the transaction/limit facts are helpful. But with a destructive mutation, three parameters, 0 required fields, and an undocumented 'permanent' switch, the description leaves the agent short of what it needs to invoke this safely.

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 only 33% (only workspace_id is documented). The description does not explain the 'permanent' flag at all, which is the highest-stakes parameter on a destructive tool — an agent cannot tell whether entries go to the deleted list or are irrecoverably purged. It also never mentions entry_ids being the batch input beyond the word 'entries'.

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), resource (journal entries), and batch semantics (multiple, single transaction, max 50), which cleanly separates it from a single-entry delete. It does not distinguish itself from the team_batch_delete_entries sibling, so an agent must infer the non-team scope from the name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance. The agent must infer that this is the multi-entry alternative to delete_entry and the non-team alternative to team_batch_delete_entries purely from naming; the description never states those conditions.

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