Permanently Delete Entry

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

The description adds meaningful context beyond the annotations: "Permanently" conveys irreversibility, and "Account-storage files are not deleted" clarifies the scope of the deletion. These details complement the destructiveHint and idempotentHint annotations without contradicting them.

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?

The description consists of two short, direct sentences that front-load the core action. Every word contributes to the meaning, making it highly concise and well-structured.

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 operation, the description covers the essential action and a key nuance (storage files not deleted), but it omits important context: the purpose of the confirm parameter, effects on attachments or references, and expected behavior if the entry does not exist. The annotations help, but the missing parameter semantics and lack of output schema leave gaps for an agent.

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 0% schema description coverage, the description must clarify parameter roles, but it does not explain bundle_id, entry_id, or confirm. The phrase "one entry" only trivially implies entry_id, and confirm remains entirely undocumented, leaving the agent without sufficient information to correctly set parameters.

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 clearly states the tool's function with a specific verb and resource: "Permanently delete one entry." The additional clarification that "Account-storage files are not deleted" helps distinguish this from related deletion operations on attachments or account storage.

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 provides no guidance on when to use this tool versus alternatives such as bundled_set_entry_state or bundled_delete_bundle. It simply describes the action without mentioning exclusions, prerequisites, or context that would help an agent decide between this and sibling tools.

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