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

Annotations already indicate destructiveHint=true and idempotentHint=true, so the description correctly states 'permanently delete' which aligns. However, it does not add context about irreversibility, potential cascading effects, or authorization requirements. The description adds minimal value beyond the annotations, but it does clarify permanence, which is slightly beyond the structured hints.

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 is only 2 sentences and is front-loaded with the action and restriction. It is concise and to the point, with no superfluous information. It could be slightly more structured, but it is efficient.

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?

Given the tool's simplicity (one param, no output schema details, annotations cover destructive nature), the description is adequate but does not address how to distinguish vault items from stock content or what happens after deletion. Since an output schema exists, return value explanation is not needed, but the restrictions and implications are not fully fleshed out.

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?

The schema description for the 'id' parameter is minimal ('Mongo `_id`'), and the tool description does not elaborate on what kind of identifier is needed or how to obtain it. Since schema coverage is 100%, but the schema description provides little semantic depth, the description should compensate but does not. It only says 'by id', which is redundant with the 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?

The description clearly states the verb 'delete' and the resource 'vault item', and explicitly notes that stock content cannot be deleted, which distinguishes it from other delete tools. It could be improved by contrasting with similar delete tools like vault_delete_character, but it is otherwise clear.

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 does not specify when to use this tool versus alternatives, such as vault_delete_character, or when not to use it. It only mentions the restriction on stock content, which is a constraint but not a usage guideline. No exclusions or alternative routing are provided.

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