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

The annotations already mark destructiveHint=true ratio, but the description goes further by stating 'Cannot be undone' and explaining 'Foundry has no item undo.' This directly informs the agent about the irreversible consequence beyond what the annotation flags.

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 concise sentences: the operation, the irreversibility warning, and the prerequisite verification step. Every sentence earns its place, and the most critical information is front-loaded.

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 simple one-parameter delete tool with destructive annotations already present, the description fully covers what the tool does, why caution is needed, and how to use it safely. No output schema is necessary for a deletion operation.

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%, with itemId described as 'World item ID to delete', so the schema already documents the only parameter. The description adds context about confirming the ID but no additional semantic detail about the parameter format or value.

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 ('world item from the Items Directory'), making the operation unambiguous. It also adds a key qualifier ('Permanently') and distinguishes the scope from generic item operations in the sibling list.

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?

Explicitly instructs the agent to use world-item-filter or world-item-get FIRST to confirm the correct ID, which is clear actionable guidance for safe use. It does not mention alternatives or exclusions, so it falls just short of a 5.

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